Triple
T684458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan de Fuca |
E13253
|
entity |
| Predicate | claimedDiscovery |
P16215
|
FINISHED |
| Object | large strait at about 47–48 degrees north latitude |
—
|
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: large strait at about 47–48 degrees north latitude | Statement: [Juan de Fuca, claimedDiscovery, large strait at about 47–48 degrees north latitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedDiscovery Context triple: [Juan de Fuca, claimedDiscovery, large strait at about 47–48 degrees north latitude]
-
A.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
B.
claimed
chosen
Indicates that an entity has asserted or stated something as true, often without definitive proof or verification.
-
C.
coDiscovererOf
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
D.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf of another entity.
-
E.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0725c708190aa6edfee742ca4e6 |
completed | March 1, 2026, 8:24 p.m. |
| PD | Predicate disambiguation | batch_69a49d1f0ccc819088c1527beabcb718 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.