Triple
T26369134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun clan |
E660722
|
entity |
| Predicate | successorStateAfterFall |
P180001
|
FINISHED |
| Object | Jin dynasty |
—
|
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: Jin dynasty | Statement: [Sun clan, successorStateAfterFall, Jin dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorStateAfterFall Context triple: [Sun clan, successorStateAfterFall, Jin dynasty]
-
A.
fallsDownBefore
Indicates that one event or entity moves downward or collapses prior in time to another specified event or entity.
-
B.
successorStateAfterDeath
Indicates the resulting state or condition that follows an entity’s death.
-
C.
consequenceOfFalling
Indicates that something occurs as a result or outcome of a falling event.
-
D.
eventuallyFalls
Indicates that an entity, after some passage of time or sequence of events, comes to fall or collapse.
-
E.
fallsOn
Indicates that one entity descends due to gravity and comes to rest upon the surface of another entity.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 26, 2026, 10:57 p.m.