Triple
T10471859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duplex A86 tunnel |
E246940
|
entity |
| Predicate | hasDeckSeparation |
P90529
|
FINISHED |
| Object | concrete slab between decks |
—
|
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: concrete slab between decks | Statement: [Duplex A86 tunnel, hasDeckSeparation, concrete slab between decks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeckSeparation Context triple: [Duplex A86 tunnel, hasDeckSeparation, concrete slab between decks]
-
A.
hasDeckType
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
B.
hasUpperDecks
Indicates that one entity possesses or includes one or more upper-level decks as part of its structure.
-
C.
hasVehicleDeck
Indicates that something (typically a vessel or structure) includes a dedicated deck or level designed for carrying or transporting vehicles.
-
D.
typeOfSeparation
chosen
Indicates the specific manner or category of separation that exists or occurred between entities.
-
E.
isThroughDeck
Indicates that one object passes completely through another object or surface, extending from one side to the other.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094cec788190a485c5c9e7cd024a |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:20 p.m.