Triple
T8229370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Composite order |
E192250
|
entity |
| Predicate | capitalPosition |
P80976
|
FINISHED |
| Object | top of column |
—
|
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: top of column | Statement: [Composite order, capitalPosition, top of column]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalPosition Context triple: [Composite order, capitalPosition, top of column]
-
A.
capital
Indicates that one place serves as the official seat of government or primary administrative center for another political entity.
-
B.
capitalRenamedFrom
Indicates that a capital city previously had a different name, specifying the former name from which it was renamed.
-
C.
capitalSince
Indicates that an entity has served as the capital of another entity starting from a specified point in time.
-
D.
capitalRenamedTo
Indicates that a place’s status or name as a capital city has been changed to a new capital designation or name.
-
E.
capitalRoleUntil
Indicates that an entity served in the role of capital of another entity up to (but not necessarily including) a specified end time.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7802417c81908837c31136c41a5c |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb3d6c34708190a987d68529cbb0b3 |
completed | March 31, 2026, 3:20 a.m. |
Created at: March 30, 2026, 5:46 p.m.