Triple
T16893570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Îles du Salut |
E424237
|
entity |
| Predicate | originallyNamedFor |
P73091
|
FINISHED |
| Object | sailors finding refuge from disease on the mainland |
—
|
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: sailors finding refuge from disease on the mainland | Statement: [Îles du Salut, originallyNamedFor, sailors finding refuge from disease on the mainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyNamedFor Context triple: [Îles du Salut, originallyNamedFor, sailors finding refuge from disease on the mainland]
-
A.
isNamedFor
Indicates that one entity bears its name in honor of, or derived from, another entity.
-
B.
isNamedForPersonFrom
Indicates that an entity is named after a person who originates from a specified place or region.
-
C.
speciesEponym
Indicates that a species is named in honor of a particular person or entity.
-
D.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
E.
historicallyNamedAfter
chosen
Indicates that one entity received its name from another entity at some point in the past.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3bbc6b97c8190b18aca477d6ef647 |
completed | April 18, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.