Triple
T24537334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | doctrina del Ejército de Chile |
E606985
|
entity |
| Predicate | esUtilizadaPor |
P22634
|
FINISHED |
| Object | unidades operativas 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: unidades operativas del Ejército de Chile | Statement: [doctrina del Ejército de Chile, esUtilizadaPor, unidades operativas del Ejército de Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esUtilizadaPor Context triple: [doctrina del Ejército de Chile, esUtilizadaPor, unidades operativas del Ejército de Chile]
-
A.
areUsedBy
chosen
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
-
B.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
C.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
D.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:26 a.m.