Triple
T21513355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U8 |
E530781
|
entity |
| Predicate | hasUndergroundAlignment |
P15152
|
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: [U8, hasUndergroundAlignment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundAlignment Context triple: [U8, hasUndergroundAlignment, true]
-
A.
hasUndergroundSection
chosen
Indicates that an entity includes a portion or segment that is located below ground level.
-
B.
hasUndergroundLevel
Indicates that one entity possesses or includes a level, floor, or section that is located below ground level.
-
C.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
-
D.
hasUndergroundDepth
Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
-
E.
hasUndergroundLength
Indicates the extent of an object or structure that lies below ground level, measured as its underground length.
- 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_69e0c45c81f08190a6b8bbb70a45aae7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea88e6fc8190a4b73b8d32dae5a8 |
completed | April 23, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:25 p.m.