Triple
T4545909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | llanero cavalry |
E110046
|
entity |
| Predicate | primaryMount |
P57642
|
FINISHED |
| Object | criollo horses |
—
|
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: criollo horses | Statement: [llanero cavalry, primaryMount, criollo horses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMount Context triple: [llanero cavalry, primaryMount, criollo horses]
-
A.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
B.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
-
C.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
D.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
E.
primaryPosition
Indicates the main role, job, or position an entity holds among potentially multiple positions.
- 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_69bd4412524c8190be5bcc9ddee91848 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57d761cc8190a7c8bdef6d130b5d |
completed | March 20, 2026, 2:21 p.m. |
| PD | Predicate disambiguation | batch_69bd5220e40481908ca2d7e2c43d8531 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:05 p.m.