Triple
T6588486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luton Airport Parkway |
E159287
|
entity |
| Predicate | hasConnectionMode |
P62886
|
FINISHED |
| Object | rail |
—
|
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: rail | Statement: [Luton Airport Parkway, hasConnectionMode, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConnectionMode Context triple: [Luton Airport Parkway, hasConnectionMode, rail]
-
A.
hasModeConnection
chosen
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
B.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
C.
hasWorkingMode
Indicates that an entity operates under or supports a particular mode or configuration of functioning.
-
D.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.