Triple
T30743241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | third voyage of Christopher Columbus |
E782746
|
entity |
| Predicate | reachedContinent |
P23314
|
FINISHED |
| Object | South America |
—
|
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: South America | Statement: [third voyage of Christopher Columbus, reachedContinent, South America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedContinent Context triple: [third voyage of Christopher Columbus, reachedContinent, South America]
-
A.
visitedContinent
Indicates that an entity has traveled to and spent time on a particular continent.
-
B.
continentOfDestination
chosen
Indicates that a specified continent is the destination location associated with an entity’s movement, travel, or targeting.
-
C.
continentOfConclusion
Indicates that a given continent is the location or scope within which a particular conclusion, result, or outcome holds or is derived.
-
D.
continentFound
Indicates that a specified continent is the location where a particular entity is found or occurs.
-
E.
livedOnContinent
Indicates that an entity resided for a period of time on a specified continent.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f6a32f081909499d6ca20f35e55 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.