Triple
T13267721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Echo Base |
E315963
|
entity |
| Predicate | statusAfterBattle |
P109227
|
FINISHED |
| Object | abandoned |
—
|
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: abandoned | Statement: [Echo Base, statusAfterBattle, abandoned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterBattle Context triple: [Echo Base, statusAfterBattle, abandoned]
-
A.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
B.
statusAfterMission
Indicates the condition or state an entity is in following the completion of a mission.
-
C.
statusAfterBattleForAzeroth
Indicates the condition or state of an entity following the events of the Battle for Azeroth.
-
D.
statusAfterRescue
Indicates the condition or state an entity is in following a rescue event or operation.
-
E.
resultOfBattle
Indicates that one entity is the outcome or consequence produced by a specific battle or combat event involving another entity.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:25 p.m.