Triple
T24537340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | doctrina del Ejército de Chile |
E606985
|
entity |
| Predicate | busca |
P34994
|
FINISHED |
| Object | unificar criterios de acción en el 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: unificar criterios de acción en el Ejército de Chile | Statement: [doctrina del Ejército de Chile, busca, unificar criterios de acción en el Ejército de Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busca Context triple: [doctrina del Ejército de Chile, busca, unificar criterios de acción en el Ejército de Chile]
-
A.
searchingFor
Indicates that one entity is actively seeking, looking for, or attempting to locate another entity.
-
B.
searchesVia
Indicates that an entity performs a search by means of, or using, a specified tool, method, or channel.
-
C.
searchFeature
Indicates that an entity provides or supports functionality for searching or querying information or items.
-
D.
searchesLedTo
Indicates that one or more search actions resulted in, or directly produced, a particular outcome or item.
-
E.
soughtTo
chosen
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
- 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.