Triple
T30778253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Bourdillon |
E783736
|
entity |
| Predicate | reachedFeature |
P164064
|
FINISHED |
| Object | South Summit of Mount Everest |
—
|
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: South Summit of Mount Everest | Statement: [Tom Bourdillon, reachedFeature, South Summit of Mount Everest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedFeature Context triple: [Tom Bourdillon, reachedFeature, South Summit of Mount Everest]
-
A.
targetFeature
Indicates that one entity is the specific feature, attribute, or characteristic that another entity is directed toward, focused on, or intended to affect.
-
B.
destinationFeature
chosen
Indicates the feature, place, or element that serves as the endpoint or target location of a movement, transfer, or directed relation.
-
C.
launchedFeature
Indicates that an entity has released or made a particular feature available for use.
-
D.
documentedFeature
Indicates that a feature has been formally recorded or described in documentation.
-
E.
throughFeature
Indicates that one entity is connected to, accessed, or achieved by means of a particular feature or characteristic of 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_69f224b213c8819083886073f90b647e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:41 p.m.