Triple
T21494841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First voyage to North America (1534) |
E530323
|
entity |
| Predicate | languageOfExpedition |
P128417
|
FINISHED |
| Object | French |
—
|
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: French | Statement: [First voyage to North America (1534), languageOfExpedition, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfExpedition Context triple: [First voyage to North America (1534), languageOfExpedition, French]
-
A.
hasLanguageOfExploration
chosen
Indicates that an entity uses or is associated with a particular language for exploration, investigation, or discovery activities.
-
B.
nationalityOfExpedition
Indicates the country or national affiliation associated with a given expedition.
-
C.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
D.
hasLanguageOfMission
Indicates that an entity (such as a mission or project) is associated with a specific language used for its communication, documentation, or operation.
-
E.
expeditionMemberOf
Indicates that an entity participates as a member in a specific expedition.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea575f2c81909cc0607c4b529f8d |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.