Triple
T9431923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina constitutional convention of 1835 |
E227397
|
entity |
| Predicate | significantEventIn |
P78702
|
FINISHED |
| Object | political history of North Carolina |
—
|
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: political history of North Carolina | Statement: [North Carolina constitutional convention of 1835, significantEventIn, political history of North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantEventIn Context triple: [North Carolina constitutional convention of 1835, significantEventIn, political history of North Carolina]
-
A.
significantEvent
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
B.
significantEventType
Indicates the specific category or kind of major or noteworthy event associated with an entity or situation.
-
C.
significantEventEnd
Indicates the point in time when a significant event or occurrence comes to a close or is considered finished.
-
D.
significantEventContext
chosen
Indicates that an event occurs within a context or circumstances that are particularly important, influential, or meaningful relative to that event.
-
E.
significantEventDocumented
Indicates that a notable or impactful event has been formally recorded or documented in some medium.
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e6059bc8190a7e98aef3caabd0b |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.