Triple
T29013411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jepson |
E737232
|
entity |
| Predicate | hasNotableGeographicFeatureNamedAfter |
P199950
|
FINISHED |
| Object | Mount Jepson |
—
|
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: Mount Jepson | Statement: [Jepson, hasNotableGeographicFeatureNamedAfter, Mount Jepson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableGeographicFeatureNamedAfter Context triple: [Jepson, hasNotableGeographicFeatureNamedAfter, Mount Jepson]
-
A.
landerNamedAfter
Indicates that one entity is a lander whose name is derived from, or given in honor of, another entity.
-
B.
notableAsNamesakeOf
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
-
C.
hasCapitalNamedAfter
Indicates that one entity serves as the capital of another entity and that this capital is named after the other entity.
-
D.
hasHeritageSiteNamedAfter
Indicates that one entity has a heritage site that is named after another entity.
-
E.
hasIslandNamedAfter
Indicates that an entity has an island that is named after it.
- F. None of above. chosen
Provenance (4 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
| PDg | Predicate description generation | batch_69ff659717708190bb56714d1b261063 |
completed | May 9, 2026, 4:49 p.m. |
Created at: April 28, 2026, 9:44 a.m.