Triple
T30953248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eurobalise |
E788602
|
entity |
| Predicate | supportsTelegramType |
P24486
|
FINISHED |
| Object | short telegram |
—
|
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: short telegram | Statement: [Eurobalise, supportsTelegramType, short telegram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTelegramType Context triple: [Eurobalise, supportsTelegramType, short telegram]
-
A.
attachmentType
Indicates the specific kind or category of attachment that relates one entity to another.
-
B.
supportsAttachments
Indicates that the subject is capable of handling or allowing the inclusion of file or data attachments in its operation or context.
-
C.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportedEntity
Indicates that one entity provides assistance, resources, or backing to another entity, enabling or sustaining its function or existence.
-
E.
supportsTopic
Indicates that one entity provides backing, endorsement, or assistance for a particular topic, idea, or subject.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:53 p.m.