Triple
T15463883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husband Hill |
E371973
|
entity |
| Predicate | summitedIn |
P118323
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Husband Hill, summitedIn, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitedIn Context triple: [Husband Hill, summitedIn, 2005]
-
A.
summited
Indicates that an entity has reached the highest point or peak of something, typically a mountain or similar elevation.
-
B.
summitedWith
Indicates that one entity reached the summit of something together with another entity, implying a joint or shared ascent.
-
C.
submittedTo
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
-
D.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
E.
firstSummitedBy
Indicates that a particular mountain or peak was first successfully climbed to its summit by a specified person or group.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1927708190a0d2b63e75469a0e |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:33 a.m.