Triple
T1562888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isla de la Juventud |
E33366
|
entity |
| Predicate | previousNameUntil |
P25649
|
FINISHED |
| Object | Isla de Pinos until 1978 |
—
|
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: Isla de Pinos until 1978 | Statement: [Isla de la Juventud, previousNameUntil, Isla de Pinos until 1978]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNameUntil Context triple: [Isla de la Juventud, previousNameUntil, Isla de Pinos until 1978]
-
A.
previousNameUsedUntil
chosen
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
B.
formerName
Indicates that an entity was previously known by a different name in the past.
-
C.
previousHonorificPrefix
Indicates that one entity was formerly used as an honorific prefix or title for another entity before being changed or replaced.
-
D.
currentNameUsedFrom
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
-
E.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.