Triple
T35991840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Spiegel Grove |
E1040866
|
entity |
| Predicate | depthToDeck |
P3822
|
FINISHED |
| Object | approximately 60–70 ft |
—
|
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: approximately 60–70 ft | Statement: [USS Spiegel Grove, depthToDeck, approximately 60–70 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depthToDeck Context triple: [USS Spiegel Grove, depthToDeck, approximately 60–70 ft]
-
A.
bodyDepth
Indicates the measurement of how deep or thick an object or body is from its front to back or outer to inner surface.
-
B.
depthOrigin
Indicates the reference point or source location from which the depth of an object or region is measured.
-
C.
depth
chosen
Indicates the vertical distance from a reference surface or top point down to a lower point or bottom within a medium or space.
-
D.
depthMetresApprox
Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
-
E.
mainDeckFloorStrength
Indicates the structural load-bearing capacity or robustness of the main deck floor in a given context.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.