Triple
T30519753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tram lines of STIB-MIVB |
E776661
|
entity |
| Predicate | dataFormatForOpenData |
P160435
|
FINISHED |
| Object | GTFS |
—
|
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: GTFS | Statement: [Tram lines of STIB-MIVB, dataFormatForOpenData, GTFS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataFormatForOpenData Context triple: [Tram lines of STIB-MIVB, dataFormatForOpenData, GTFS]
-
A.
dataAvailableAs
Indicates that specific data can be accessed or obtained in a particular form, format, or representation.
-
B.
openFormat
chosen
Indicates that an entity is presented or made available in a format that is open, accessible, and not restricted by proprietary constraints.
-
C.
dataDatatype
Indicates that a piece of data is associated with, or constrained to, a specific datatype.
-
D.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
E.
dataTypeContributed
Indicates that an entity has provided or supplied a particular type or category of data.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6880930e4819084605c33854cf72a |
completed | May 2, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:17 p.m.