Triple
T27167401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viejo Mundo |
E682814
|
entity |
| Predicate | tieneEquivalenteEnItaliano |
P48373
|
FINISHED |
| Object | Vecchio Mondo |
—
|
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: Vecchio Mondo | Statement: [Viejo Mundo, tieneEquivalenteEnItaliano, Vecchio Mondo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieneEquivalenteEnItaliano Context triple: [Viejo Mundo, tieneEquivalenteEnItaliano, Vecchio Mondo]
-
A.
equivalentTitleInItalian
chosen
Indicates that one entity’s title is an equivalent version of another entity’s title expressed in Italian.
-
B.
cognateInItalian
Indicates that a word has a cognate (a related word with a common etymological origin) in Italian.
-
C.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
D.
equivalentInZapotec
Indicates that two linguistic elements are equivalent in meaning or function within the Zapotec language.
-
E.
correspondsToAbbreviationInItalian
Indicates that one entity is the full form or concept for which the other entity serves as an abbreviation in Italian.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 9:21 a.m.