Triple
T28187380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yehenara clan |
E716214
|
entity |
| Predicate | notableEventInHistoryOf |
P129680
|
FINISHED |
| Object | Xinyou Coup (1861) |
—
|
NE NERFINISHED |
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: Xinyou Coup (1861) | Statement: [Yehenara clan, notableEventInHistoryOf, Xinyou Coup (1861)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventInHistoryOf Context triple: [Yehenara clan, notableEventInHistoryOf, Xinyou Coup (1861)]
-
A.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
B.
chronologicallyNotableEvent
Indicates that an event is significant or noteworthy in terms of its position or impact within a chronological sequence of events.
-
C.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
D.
notableEventIncluded
chosen
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
-
E.
notableInternationalEvents
Indicates that the subject is associated with significant events that have international relevance or impact.
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: April 27, 2026, 10:23 p.m.