Triple
T19393602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cromwell Current |
E485128
|
entity |
| Predicate | positionRelativeToSurface |
P136277
|
FINISHED |
| Object | subsurface |
—
|
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: subsurface | Statement: [Cromwell Current, positionRelativeToSurface, subsurface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToSurface Context triple: [Cromwell Current, positionRelativeToSurface, subsurface]
-
A.
positionRelativeToBuilding
Indicates the spatial relationship of an entity’s location with respect to a specific building (e.g., in front of, behind, adjacent to, on top of).
-
B.
locationRelativeToPitch
Indicates the spatial position of an entity in relation to the pitch (e.g., above, beside, or within the pitch area).
-
C.
positionRelativeToHod
Indicates the spatial or positional relationship of an entity with respect to a specified hod (a particular reference point or unit in a structured space).
-
D.
positionRelativeToBridge
Indicates the spatial position of an entity in relation to a specific bridge, such as being on, under, near, or adjacent to it.
-
E.
relativePositionInSystem
Indicates the spatial or ordered position an entity occupies within a larger system or structured arrangement.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b468dd88190acd82b4ee33bd39b |
completed | April 20, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69e50213571881909cd7543a43b51986 |
completed | April 19, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.