Triple
T27151904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ralph Middleton Munroe’s boat “Dodge” |
E682411
|
entity |
| Predicate | allegedNamesakeOf |
P132742
|
FINISHED |
| Object | Dodge Island |
—
|
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: Dodge Island | Statement: [Ralph Middleton Munroe’s boat “Dodge”, allegedNamesakeOf, Dodge Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedNamesakeOf Context triple: [Ralph Middleton Munroe’s boat “Dodge”, allegedNamesakeOf, Dodge Island]
-
A.
allegedAncestor
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
B.
usedAsNamesakeFor
chosen
Indicates that one entity serves as the source or inspiration for the name given to another entity.
-
C.
hadEponymousAncestor
Indicates that an entity has an ancestor whose name it shares or from whom its own name is derived.
-
D.
hasHonorificNamesake
Indicates that an entity is named in honor of another entity, serving as a namesake that recognizes or commemorates the other.
-
E.
successorNamesake
Indicates that one entity is named after another entity that precedes it, typically as its successor or continuation in name.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 9:14 a.m.