Triple
T15455040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Thousand Greek mercenaries |
E371747
|
entity |
| Predicate | statusAfterCunaxa |
P118874
|
FINISHED |
| Object | stranded deep in hostile territory |
—
|
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: stranded deep in hostile territory | Statement: [Ten Thousand Greek mercenaries, statusAfterCunaxa, stranded deep in hostile territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterCunaxa Context triple: [Ten Thousand Greek mercenaries, statusAfterCunaxa, stranded deep in hostile territory]
-
A.
statusAfterSmaug
Indicates the resulting status or condition of an entity after an event or interaction involving Smaug has occurred.
-
B.
statusAfter1569
Indicates the status or condition an entity has after the year 1569, typically contrasting it with its prior status.
-
C.
statusAfter1806
Indicates the status or condition of an entity specifically in the period following the year 1806.
-
D.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
E.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f131b1481909ff099c3b844ee07 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:31 a.m.