Triple
T5416591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolinian |
E121146
|
entity |
| Predicate | statehoodOfState |
P14008
|
FINISHED |
| Object | 1789 |
—
|
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: 1789 | Statement: [North Carolinian, statehoodOfState, 1789]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statehoodOfState Context triple: [North Carolinian, statehoodOfState, 1789]
-
A.
statehoodStatus
Indicates the legal or political condition of an entity regarding whether, how, or to what extent it is recognized or functions as a state.
-
B.
statehoodContext
Indicates the contextual circumstances, conditions, or framework under which an entity’s status as a state (or its statehood) is defined, recognized, or discussed.
-
C.
foundingState
Indicates that a state or entity played a primary role in establishing or creating another organization, institution, or political entity.
-
D.
statehoodYear
Indicates the year in which an entity officially became a recognized state or attained statehood status.
-
E.
statehoodFrom
chosen
Indicates the point in time from which an entity has held official statehood or recognized status as a state.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bff75881909bdfd2cdf7ff5657 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.