Triple
T32572976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Zhuangxiang of Qin |
E832564
|
entity |
| Predicate | hostageStatus |
P75973
|
FINISHED |
| Object | hostage in the State of Zhao |
—
|
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: hostage in the State of Zhao | Statement: [King Zhuangxiang of Qin, hostageStatus, hostage in the State of Zhao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostageStatus Context triple: [King Zhuangxiang of Qin, hostageStatus, hostage in the State of Zhao]
-
A.
hostageOutcome
Indicates the result or final status of a hostage situation, such as whether hostages were released, rescued, harmed, or remained captive.
-
B.
hostages
Indicates that one party is forcibly holding another party captive, typically to compel a third party to meet certain demands or conditions.
-
C.
hostageLocation
chosen
Indicates that a person or group is being held as a hostage at a specific location.
-
D.
hostagePower
Indicates that one entity exerts power or leverage over another by holding someone or something important to that other entity as a hostage.
-
E.
wasHostageIn
Indicates that an entity was held as a hostage at or within a specified place or context.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63ca2e881909f8e056c1ed181ba |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.