Triple
T30654356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guerra de Tres Años |
E780344
|
entity |
| Predicate | nombre alternativo |
P110696
|
FINISHED |
| Object | Guerra de Reforma |
—
|
NE NERFINISHED |
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: Guerra de Reforma | Statement: [Guerra de Tres Años, nombre alternativo, Guerra de Reforma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nombre alternativo Context triple: [Guerra de Tres Años, nombre alternativo, Guerra de Reforma]
-
A.
hasAlternativeFamilyName
Indicates that an entity is associated with an additional or variant family name besides its primary family name.
-
B.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
-
C.
alternativeNameMeaning
Indicates that one entity expresses the meaning or interpretation of an alternative name used for another entity.
-
D.
haveAlternativeTitle
chosen
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
E.
knownAsBy
Indicates that one entity is referred to or recognized by another entity using a particular name or designation.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a9a4d9081909d67b4dc73642cae |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.