Triple
T29577778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conshelf II |
E753490
|
entity |
| Predicate | deeperStationDepth |
P55576
|
FINISHED |
| Object | about 25 metres for deep cabin |
—
|
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: about 25 metres for deep cabin | Statement: [Conshelf II, deeperStationDepth, about 25 metres for deep cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deeperStationDepth Context triple: [Conshelf II, deeperStationDepth, about 25 metres for deep cabin]
-
A.
deepestStation
Indicates that one station in a network or system is located at a greater depth (e.g., below ground or sea level) than all other stations.
-
B.
deepestStationDepthMeters
chosen
Indicates the maximum depth, in meters, reached by any station associated with the subject.
-
C.
oneOfDeepestStationsIn
Indicates that a station is among the deepest stations located within a specified area or system.
-
D.
designedTargetDepthInKilometers
Indicates the intended or planned depth, measured in kilometers, that something is designed to reach or operate at.
-
E.
depthBelowSurfaceInMeters
Indicates the vertical distance, measured in meters, that something is located below a reference surface level.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:04 p.m.