Triple
T30519751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tram lines of STIB-MIVB |
E776661
|
entity |
| Predicate | hasMapOn |
P138987
|
FINISHED |
| Object | STIB-MIVB official website |
—
|
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: STIB-MIVB official website | Statement: [Tram lines of STIB-MIVB, hasMapOn, STIB-MIVB official website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapOn Context triple: [Tram lines of STIB-MIVB, hasMapOn, STIB-MIVB official website]
-
A.
hasMaps
chosen
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
B.
hasMapBy
Indicates that one entity is represented, depicted, or detailed by a specific map associated with it.
-
C.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
-
D.
hasMapframe
Indicates that an entity is associated with an embedded, interactive map frame representation of its geographic location or area.
-
E.
hasMapCode
Indicates that an entity is associated with a specific map-related code or identifier.
- 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_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: April 29, 2026, 8:17 p.m.