Triple
T3579773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bagshot railway station |
E75770
|
entity |
| Predicate | hasCISDisplays |
P49832
|
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: [Bagshot railway station, hasCISDisplays, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCISDisplays Context triple: [Bagshot railway station, hasCISDisplays, yes]
-
A.
hasReplicaDisplays
Indicates that an entity features or presents one or more replica items as displays.
-
B.
CISStatus
Indicates the compliance or certification status of an entity with respect to CIS (Center for Internet Security) benchmarks or standards.
-
C.
hasDisplayType
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
D.
includesDisplayEngine
Indicates that one entity contains or incorporates another entity that functions as a display engine.
-
E.
hasOuterDisplay
Indicates that one entity serves as the external or outward-facing display component of another entity.
- 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_69ad85d5e3008190bdfe0bacdd1f5a1b |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0ffecdc8190bf01c8ba90e3733e |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:21 p.m.