Triple
T12792470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shining Wall |
E305802
|
entity |
| Predicate | knownAmong |
P65126
|
FINISHED |
| Object | elite mountaineers |
—
|
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: elite mountaineers | Statement: [Shining Wall, knownAmong, elite mountaineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownAmong Context triple: [Shining Wall, knownAmong, elite mountaineers]
-
A.
knownIn
chosen
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
B.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
C.
knownPrimarilyThrough
Indicates that one entity is chiefly recognized, identified, or made familiar to others by means of another entity (such as a work, role, medium, or context).
-
D.
acquaintanceOf
Indicates that one entity knows another in a casual or non-intimate way, without implying close friendship or strong personal ties.
-
E.
followersKnownAs
Indicates that the followers of an entity are referred to by a particular name or label.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6b55248190ab938e69eb263612 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.