Triple
T17803386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covent Garden station |
E444490
|
entity |
| Predicate | hasPlatformDepth |
P89425
|
FINISHED |
| Object | deep below street level |
—
|
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: deep below street level | Statement: [Covent Garden station, hasPlatformDepth, deep below street level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlatformDepth Context triple: [Covent Garden station, hasPlatformDepth, deep below street level]
-
A.
hasDeepPlatform
chosen
Indicates that one entity possesses or provides a platform characterized by significant depth, capability, or extensiveness in supporting another entity’s activities or functions.
-
B.
hasPortDepth
Indicates that a port possesses a specific water depth suitable for accommodating vessels.
-
C.
hasChannelDepth
Indicates that one entity specifies or records the depth measurement of a channel associated with another entity.
-
D.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
E.
plateInterfaceDepthRange
Indicates the range of depths over which two tectonic plates are in contact or interacting at their interface.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4880171608190be2088c7a387bfb7 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.