Triple
T31518573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keroman submarine base |
E804142
|
entity |
| Predicate | roofThickness |
P172262
|
FINISHED |
| Object | up to several meters |
—
|
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: up to several meters | Statement: [Keroman submarine base, roofThickness, up to several meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roofThickness Context triple: [Keroman submarine base, roofThickness, up to several meters]
-
A.
wallThicknessComparedTo
Indicates how the thickness of one wall relates to the thickness of another wall, typically in terms of being greater, equal, or less.
-
B.
domeThickness
Indicates the measured or specified thickness of a dome structure in the relationship.
-
C.
wallThicknessOfKeep
Indicates the thickness of the walls of a keep in a fortification or castle.
-
D.
archDepthAtRoof
Indicates the depth or vertical extent of an arch measured specifically at the roof level.
-
E.
heatShieldThickness
Indicates the thickness of a protective heat shield used to guard an object from high temperatures or thermal loads.
- F. None of above. chosen
Provenance (4 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a915ead881909463ae46419c343e |
completed | May 3, 2026, 1:47 a.m. |
Created at: April 30, 2026, 9:54 p.m.