Triple
T20785317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Consort |
E511614
|
entity |
| Predicate | positionRelativeToPower |
P141534
|
FINISHED |
| Object | secondary |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: secondary | Statement: [The Consort, positionRelativeToPower, secondary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToPower Context triple: [The Consort, positionRelativeToPower, secondary]
-
A.
positionOnStatePower
Indicates a stance or viewpoint an entity holds regarding the nature, scope, or use of state power.
-
B.
powerRangeRelativeTo
Indicates the comparative span or limits of power one entity has relative to another entity or reference standard.
-
C.
positionRelativeToHod
Indicates the spatial or positional relationship of an entity with respect to a specified hod (a particular reference point or unit in a structured space).
-
D.
positionRelativeToTower
Indicates the spatial relationship or placement of an entity with respect to a specified tower.
-
E.
positionRelativeToBuilding
Indicates the spatial relationship of an entity’s location with respect to a specific building (e.g., in front of, behind, adjacent to, on top of).
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e0b4cac7a48190a715cb3d545df2b4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c28b4ce88190a45f1c99b58d18eb |
completed | April 21, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e5c0550ec481908a0877fb2409d983 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:38 p.m.