Triple
T8711614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953 British Mount Everest expedition |
E206789
|
entity |
| Predicate | summitDate |
P70845
|
FINISHED |
| Object | 1953-05-29 |
—
|
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: 1953-05-29 | Statement: [1953 British Mount Everest expedition, summitDate, 1953-05-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitDate Context triple: [1953 British Mount Everest expedition, summitDate, 1953-05-29]
-
A.
summitDayFrom
Indicates the specific day on which a summit or peak event occurs relative to a given timeframe or schedule.
-
B.
firstSummitDate
chosen
Indicates the calendar date on which an entity (such as a person or team) first reached the summit of a particular peak or completed its initial summit ascent.
-
C.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
D.
holdsSummit
Indicates that an entity organizes and conducts a formal summit meeting or conference with others.
-
E.
summitCount
Indicates the number of summits or peak ascents associated with an 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c3189f88190bb9bb77ba9d28d60 |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.