Triple
T4301980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omaha |
E99857
|
entity |
| Predicate | enrolledMembersIn21stCentury |
P55344
|
FINISHED |
| Object | several thousand |
—
|
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: several thousand | Statement: [Omaha, enrolledMembersIn21stCentury, several thousand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enrolledMembersIn21stCentury Context triple: [Omaha, enrolledMembersIn21stCentury, several thousand]
-
A.
statusAsOf21stCentury
Indicates that the status or condition of an entity is evaluated or defined specifically as it stands in the 21st century.
-
B.
eligibleMembers
Indicates that certain entities meet the required criteria or conditions to be considered eligible members of a specified group or category.
-
C.
statusIn20thCentury
Indicates that an entity held a particular status, condition, or classification specifically during the 20th century.
-
D.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
E.
signedInCentury
Indicates that an entity (such as a document, treaty, or agreement) was signed during a specified century.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350b66450819089c9ff6ff9f045e5 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:08 p.m.