Triple
T3467172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Seringapatam |
E73164
|
entity |
| Predicate | hostages |
P48966
|
FINISHED |
| Object | two sons of Tipu Sultan |
—
|
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: two sons of Tipu Sultan | Statement: [Treaty of Seringapatam, hostages, two sons of Tipu Sultan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostages Context triple: [Treaty of Seringapatam, hostages, two sons of Tipu Sultan]
-
A.
numberOfHostages
Indicates the quantity of hostages involved in a particular situation, event, or context.
-
B.
abductedBy
Indicates that an entity has been forcibly taken or carried away by another entity against their will.
-
C.
prisonerExchange
Indicates a relationship where one party transfers prisoners to another party in return for receiving other prisoners or concessions in exchange.
-
D.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
E.
numberOfHijackers
Indicates the quantity of individuals who carried out or attempted to carry out a hijacking in the described event or context.
- 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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb1090188190ac8aafd87dfaa6a7 |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.