Triple
T23759741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Jiang |
E587216
|
entity |
| Predicate | vassalStateRuled |
P135339
|
FINISHED |
| Object | Qi |
—
|
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: Qi | Statement: [House of Jiang, vassalStateRuled, Qi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vassalStateRuled Context triple: [House of Jiang, vassalStateRuled, Qi]
-
A.
vassalState
Indicates a relationship where one political entity is subordinate to and under the authority or control of another, typically more powerful, state.
-
B.
stateRuled
Indicates that a particular state is governed or controlled by a specified ruler or ruling entity.
-
C.
alsoRuled
Indicates that two or more entities shared ruling authority over the same domain or subjects, either concurrently or at different times.
-
D.
governmentFormOfRuledState
Indicates the type of governmental system or structure by which a particular state or territory is ruled.
-
E.
governingStateInHistory
chosen
Indicates that one state historically exercised governing authority or control over another entity during a specific period in the past.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bdb1d6348190afb3f0fbea1b9ca3 |
completed | April 29, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:14 p.m.