Triple
T26690727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Mount Everest Expedition 1952 |
E672872
|
entity |
| Predicate | includedSherpaTeam |
P29737
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Swiss Mount Everest Expedition 1952, includedSherpaTeam, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedSherpaTeam Context triple: [Swiss Mount Everest Expedition 1952, includedSherpaTeam, yes]
-
A.
includesTeam
chosen
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
B.
includesTeamsThat
Indicates that an entity contains or encompasses specific teams as part of its composition or scope.
-
C.
teamSizeVariantOf
Indicates that one entity represents a variation of another entity specifically in terms of team size configuration or composition.
-
D.
teamIncludes
Indicates that a particular team has a specified member or entity as part of its composition.
-
E.
teamUpWith
Indicates forming a cooperative partnership or alliance with another entity to work together toward a shared goal.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 27, 2026, 3:25 a.m.