Triple
T18201687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ID |
E435804
|
entity |
| Predicate | representsEntityWithAdmissionOrder |
P128000
|
FINISHED |
| Object | 43rd U.S. state |
—
|
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: 43rd U.S. state | Statement: [ID, representsEntityWithAdmissionOrder, 43rd U.S. state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsEntityWithAdmissionOrder Context triple: [ID, representsEntityWithAdmissionOrder, 43rd U.S. state]
-
A.
admissionOrder
Indicates the sequence or priority in which admissions occur or are processed relative to one another.
-
B.
admittedEntity
Indicates that one entity has been formally accepted, received, or allowed entry by another entity (such as an institution, organization, or location).
-
C.
entityRepresents
chosen
Indicates that one entity stands for, symbolizes, or serves as a representation of another entity.
-
D.
admittedSuccessorEntity
Indicates that one entity has been formally accepted or recognized as the successor or replacement of another entity.
-
E.
administrativeStatusOfEntityRepresented
Indicates the current administrative or operational status assigned to the entity that is being represented.
- F. None of above.
Provenance (3 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d71f288190918ca78543118bbe |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.