Triple
T16053116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summus Poeninus |
E389404
|
entity |
| Predicate | isAboveTunnel |
P67400
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Summus Poeninus, isAboveTunnel, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAboveTunnel Context triple: [Summus Poeninus, isAboveTunnel, true]
-
A.
isInTunnelSystem
Indicates that one entity is located within or forms part of a tunnel system associated with another entity.
-
B.
partOfTunnel
Indicates that one entity forms a physical segment or component within the structure or extent of a tunnel.
-
C.
hasRailwayTunnel
Indicates that one entity contains, includes, or is connected by a railway tunnel associated with the other entity.
-
D.
hasSummitTunnel
Indicates that a summit or peak contains or is traversed by a tunnel.
-
E.
crossedByTunnel
chosen
Indicates that one entity (typically a barrier like a mountain, river, or road) is traversed or passed through by another entity via a tunnel.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.