Triple
T899881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University of North Carolina at Chapel Hill |
E19422
|
entity |
| Predicate | instructionBegan |
P21164
|
FINISHED |
| Object | 1795 |
—
|
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: 1795 | Statement: [University of North Carolina at Chapel Hill, instructionBegan, 1795]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: instructionBegan Context triple: [University of North Carolina at Chapel Hill, instructionBegan, 1795]
-
A.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
B.
occupationBegan
Indicates the point in time when an entity started holding a particular occupation or job.
-
C.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
D.
began
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
E.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad42ecac81909f8bc554d2fe0363 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4abb157d08190a7d7281eb3f1b788 |
completed | March 1, 2026, 9:12 p.m. |
Created at: March 1, 2026, 7:39 p.m.