Triple
T3565747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruxelles-Nord / Brussel-Noord |
E75442
|
entity |
| Predicate | hasTramConnection |
P17788
|
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: [Bruxelles-Nord / Brussel-Noord, hasTramConnection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTramConnection Context triple: [Bruxelles-Nord / Brussel-Noord, hasTramConnection, yes]
-
A.
hasTramway
chosen
Indicates that a location or area is served by, contains, or is connected to a tramway system.
-
B.
hasPublicTransportConnection
Indicates that there is an available public transportation link or service connecting the related entities.
-
C.
hasTramDestination
Indicates that a tram route or service goes to or terminates at a specified destination.
-
D.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
E.
hasUndergroundConnections
Indicates that one entity is linked to another through subterranean or hidden passageways, networks, or channels.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0a8f6288190928479f5bea32245 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.