Triple
T14698551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Apamea |
E345227
|
entity |
| Predicate | requiredHostages |
P93548
|
FINISHED |
| Object | Seleucid royal hostages to Rome |
—
|
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: Seleucid royal hostages to Rome | Statement: [Treaty of Apamea, requiredHostages, Seleucid royal hostages to Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredHostages Context triple: [Treaty of Apamea, requiredHostages, Seleucid royal hostages to Rome]
-
A.
numberOfHostages
Indicates the quantity of hostages involved in a particular situation, event, or context.
-
B.
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.
-
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.
numberOfHostagesKilled
Indicates the number of hostages who were killed in the context of a specific event or situation.
-
E.
takesHostageDuring
Indicates that one entity seizes and holds another entity as a hostage in the course of a particular event or action.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb604f88081908a677175045496d0 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.