Triple
T30255687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matsudaira Takechiyo |
E769334
|
entity |
| Predicate | servedAsHostageOf |
P93548
|
FINISHED |
| Object | Oda clan |
—
|
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: Oda clan | Statement: [Matsudaira Takechiyo, servedAsHostageOf, Oda clan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsHostageOf Context triple: [Matsudaira Takechiyo, servedAsHostageOf, Oda clan]
-
A.
wasHostageIn
Indicates that an entity was held as a hostage at or within a specified place or context.
-
B.
heldHostagesFor
Indicates that one party unlawfully detained another party or parties as hostages for a period of time, typically to exert pressure or gain leverage.
-
C.
hostages
Indicates that one party is forcibly holding another party captive, typically to compel a third party to meet certain demands or conditions.
-
D.
grantedHostages
chosen
Indicates that one party has given or handed over hostages to another party, typically as a guarantee or security in an agreement or conflict.
-
E.
numberOfHostages
Indicates the quantity of hostages involved in a particular situation, event, 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 29, 2026, 7:41 p.m.