Triple
T5046029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Kingdom and France |
E113665
|
entity |
| Predicate | ChannelTunnelLocation |
P51738
|
FINISHED |
| Object | between Folkestone and Coquelles |
—
|
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: between Folkestone and Coquelles | Statement: [United Kingdom and France, ChannelTunnelLocation, between Folkestone and Coquelles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChannelTunnelLocation Context triple: [United Kingdom and France, ChannelTunnelLocation, between Folkestone and Coquelles]
-
A.
transmitterLocation
Indicates the spatial position or place where a transmitter is situated or operates.
-
B.
locationOfBroadcast
Indicates the place or geographic area from which a broadcast is transmitted or originates.
-
C.
crewLocation
Indicates that a crew is located at, assigned to, or present in a specific place or environment.
-
D.
partOfTunnel
Indicates that one entity forms a physical segment or component within the structure or extent of a tunnel.
-
E.
connectsLocation
chosen
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fe99688190961708f5d8eb6bff |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.