Triple
T24165918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mando del Ejército de Chile |
E598984
|
entity |
| Predicate | incluyeNivel |
P89909
|
FINISHED |
| Object | alto mando del Ejército de Chile |
—
|
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: alto mando del Ejército de Chile | Statement: [mando del Ejército de Chile, incluyeNivel, alto mando del Ejército de Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incluyeNivel Context triple: [mando del Ejército de Chile, incluyeNivel, alto mando del Ejército de Chile]
-
A.
containsLevel
chosen
Indicates that one entity includes or encompasses a specific level or layer within its structure or hierarchy.
-
B.
coversLevel
Indicates that one entity includes or encompasses a particular level or layer of another entity or system.
-
C.
hasLevel
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
D.
definesLevel
Indicates that one entity specifies or establishes the degree, stage, or intensity at which another entity is set or operates.
-
E.
followsLevel
Indicates that one entity comes after or succeeds another in a defined sequence, stage, or hierarchical level.
- 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_69e288cbd62881909de32ca64a70c17b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:32 p.m.