Triple
T3455859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zumsteinspitze |
E72901
|
entity |
| Predicate | SOIUSACode |
P9567
|
FINISHED |
| Object | I/B-9.III-A.3.b |
—
|
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: I/B-9.III-A.3.b | Statement: [Zumsteinspitze, SOIUSACode, I/B-9.III-A.3.b]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SOIUSACode Context triple: [Zumsteinspitze, SOIUSACode, I/B-9.III-A.3.b]
-
A.
FIBACode
Indicates a relationship where an entity is assigned or associated with a specific FIBA (International Basketball Federation) identification code.
-
B.
usesSoC
Indicates that one entity incorporates or relies on a particular system-on-chip (SoC) as a core hardware component for its operation.
-
C.
isOfficialCodeFor
chosen
Indicates that one entity serves as the formally recognized or authorized code that designates or identifies another entity.
-
D.
seaCode
Indicates a standardized code or identifier assigned to a sea or maritime area.
-
E.
inseeCode
Indicates the official INSEE (French national statistics institute) code assigned to an entity, typically identifying a specific geographic or administrative unit.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbaa77b9c81909376a5995cdaf6ac |
completed | March 8, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69adae041d588190a84a02bca94adec8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.