Triple
T32923438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belfast to Antrim corridor |
E842204
|
entity |
| Predicate | connectsBeyond |
P198656
|
FINISHED |
| Object | North Antrim |
—
|
NE NERFINISHED |
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: North Antrim | Statement: [Belfast to Antrim corridor, connectsBeyond, North Antrim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsBeyond Context triple: [Belfast to Antrim corridor, connectsBeyond, North Antrim]
-
A.
helpedConnect
Indicates that one entity assisted in establishing or facilitating a connection or relationship between two or more other entities.
-
B.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
C.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
D.
connectsMine
Indicates that one entity is linked or joined to another entity in the context of a mine or mining-related structure.
-
E.
connectsWorld
Indicates a relationship in which one entity links or bridges different worlds, realms, or domains, enabling interaction or transition between them.
- F. None of above. chosen
Provenance (4 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
| PDg | Predicate description generation | batch_69fefa05757481908fa38f5c604afbbe |
completed | May 9, 2026, 9:10 a.m. |
Created at: May 1, 2026, 1:20 a.m.