Triple
T27541311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dayuan |
E695241
|
entity |
| Predicate | reasonSoughtBy |
P24494
|
FINISHED |
| Object | acquisition of heavenly horses |
—
|
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: acquisition of heavenly horses | Statement: [Dayuan, reasonSoughtBy, acquisition of heavenly horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonSoughtBy Context triple: [Dayuan, reasonSoughtBy, acquisition of heavenly horses]
-
A.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
B.
reasonForInquisitionInquiry
Indicates the underlying cause, motive, or circumstance that led to an inquisition initiating an inquiry into a person, group, or matter.
-
C.
reasonForLocation
Indicates the cause, purpose, or justification for why an entity is at a particular location.
-
D.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
E.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 1:31 p.m.