Triple
T26943562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echo |
E678578
|
entity |
| Predicate | statusDuringCitadelArc |
P180770
|
FINISHED |
| Object | presumed dead |
—
|
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: presumed dead | Statement: [Echo, statusDuringCitadelArc, presumed dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusDuringCitadelArc Context triple: [Echo, statusDuringCitadelArc, presumed dead]
-
A.
roleInCitadel
Indicates the specific function, position, or responsibility an entity holds within a citadel or fortified complex.
-
B.
citadelAlsoCalled
Indicates that a citadel is known or referred to by an alternative name or alias.
-
C.
statusAfterCunaxa
Indicates the status or condition of an entity following the events of the Battle of Cunaxa.
-
D.
allegianceArc
Indicates a change or evolution in an entity’s loyalty or allegiance to another entity over time.
-
E.
statusUnderARC
Indicates that one entity’s status is defined, governed, or classified according to the rules or framework of an ARC (e.g., a specific regulatory, review, or control system).
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: April 27, 2026, 6:20 a.m.