Triple
T28700677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Cruz de la Orden del Mérito Civil |
E729540
|
entity |
| Predicate | seDistingueDe |
P60828
|
FINISHED |
| Object | condecoraciones militares españolas |
—
|
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: condecoraciones militares españolas | Statement: [Gran Cruz de la Orden del Mérito Civil, seDistingueDe, condecoraciones militares españolas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seDistingueDe Context triple: [Gran Cruz de la Orden del Mérito Civil, seDistingueDe, condecoraciones militares españolas]
-
A.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
B.
neDoitPasÊtreConfonduAvec
Indicates that one entity should not be mistaken for, or confused with, another distinct entity.
-
C.
differIn
Indicates that two entities are not the same in at least one specified aspect, attribute, or value.
-
D.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
E.
categoryDistinguishedFrom
chosen
Indicates that one category is explicitly distinguished from another, clarifying that they are separate and should not be confused.
- 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_69f043e6e9688190b6bdd6e5665498ff |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656b4097c8190b6a99be60bc8b670 |
completed | May 2, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:42 a.m.