Triple
T25207197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hallam railway station |
E631284
|
entity |
| Predicate | hasUndercoverAreas |
P110145
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hallam railway station, hasUndercoverAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndercoverAreas Context triple: [Hallam railway station, hasUndercoverAreas, yes]
-
A.
hasSecretArea
Indicates that an entity contains or is associated with a hidden or restricted area not normally accessible or visible.
-
B.
undercoverFor
Indicates that one entity is secretly acting on behalf of or within another entity, typically to gather information or carry out covert objectives without revealing their true affiliation.
-
C.
hasShelteredAreas
chosen
Indicates that one entity provides or contains areas that offer protection or cover for another entity.
-
D.
hasSecretExits
Indicates that an entity possesses one or more hidden or concealed exits that are not part of its normal, visible access points.
-
E.
hasUndergroundOrgan
Indicates that an entity possesses an organ or structure that is located below the ground surface.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 12:52 p.m.