Triple
T28242563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John A. Martin |
E712070
|
entity |
| Predicate | has part named after |
P107513
|
FINISHED |
| Object | John Martin Reservoir |
—
|
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: John Martin Reservoir | Statement: [John A. Martin, has part named after, John Martin Reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has part named after Context triple: [John A. Martin, has part named after, John Martin Reservoir]
-
A.
hasPlaceNamedAfter
Indicates that one place is named in honor of or derived from the name of another place.
-
B.
hasPartiallyNamedAfter
Indicates that one entity is partially named in reference to another entity, such that only a portion of its name derives from or honors the other.
-
C.
hasNamedAfterPerson
chosen
Indicates that one entity is named in honor of, or derived from the name of, a specific person.
-
D.
hasPartInHisHonor
Indicates that something includes or contains a part, section, or component that is dedicated or named in honor of a particular person.
-
E.
hasHeritageSiteNamedAfter
Indicates that one entity has a heritage site that is named after another entity.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c650c48190a9502750933f3ba0 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:59 p.m.