Triple
T4822690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cupar railway station |
E107744
|
entity |
| Predicate | hasInformationSystem |
P5881
|
FINISHED |
| Object | digital departure boards |
—
|
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: digital departure boards | Statement: [Cupar railway station, hasInformationSystem, digital departure boards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInformationSystem Context triple: [Cupar railway station, hasInformationSystem, digital departure boards]
-
A.
hasInformationService
chosen
Indicates that one entity provides, operates, or is associated with an information-related service for another entity.
-
B.
hasPASystem
Indicates that an entity possesses or is equipped with a public address (PA) system.
-
C.
hasBaseSystem
Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
-
D.
systemFlagship
Indicates that an entity serves as the primary or leading representative (flagship) within a larger system or collection of related entities.
-
E.
hasDevelopmentSystem
Indicates that one entity possesses, uses, or is associated with a particular system, platform, or environment used for development activities.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.