Triple
T15319623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Niguarda |
E366253
|
entity |
| Predicate | hasTramLine |
P17788
|
FINISHED |
| Object | Tram line 4 |
E857886
|
NE 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: Tram line 4 | Statement: [Niguarda, hasTramLine, Tram line 4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tram line 4 Context triple: [Niguarda, hasTramLine, Tram line 4]
-
A.
Tram line 4
chosen
Tram line 4 is one of Budapest’s busiest urban tram routes, running across the city center and connecting major hubs including Nyugati tér.
-
B.
Tram 14
Tram 14 is a major tram line in Geneva’s public transport system, connecting key districts and suburbs within the city.
-
C.
Tram line 6
Tram line 6 is one of Budapest’s busiest and most frequent tram routes, running along the Grand Boulevard and serving major hubs such as Nyugati tér.
-
D.
Tram 15
Tram 15 is a major tram line in Geneva’s public transport system, connecting key districts across the city and its suburbs.
-
E.
Tram 17
Tram 17 is a tram line in Geneva’s public transport system operated by the city’s transit authority.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd356b881908f054b64eee6a371 |
completed | April 16, 2026, 1:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef8a9085881909904152c32b0fed1 |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:16 a.m.