Triple
T24777317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | da Gama |
E619894
|
entity |
| Predicate | toponymicUse |
P20238
|
FINISHED |
| Object | Vasco da Gama (city in India named after Vasco da Gama) |
—
|
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: Vasco da Gama (city in India named after Vasco da Gama) | Statement: [da Gama, toponymicUse, Vasco da Gama (city in India named after Vasco da Gama)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toponymicUse Context triple: [da Gama, toponymicUse, Vasco da Gama (city in India named after Vasco da Gama)]
-
A.
hasToponymicUse
chosen
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
B.
usedAsToponymicBy
Indicates that one entity is employed as a place-based surname or name-forming element for another entity.
-
C.
toponymicFunction
Indicates that one entity functions as a place-related name or designation for another entity, typically identifying or characterizing it by a geographic location.
-
D.
hasToponymicMotivation
Indicates that something is motivated, derived, or named based on a place name (toponym).
-
E.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
- 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_69e2fabd04488190a2d13c97be745a2d |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:38 a.m.