Triple
T22295307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A36 motorway (Portugal) |
E551101
|
entity |
| Predicate | hasJunctionWith |
P1018
|
FINISHED |
| Object | IC19 |
—
|
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: IC19 | Statement: [A36 motorway (Portugal), hasJunctionWith, IC19]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IC19 Context triple: [A36 motorway (Portugal), hasJunctionWith, IC19]
-
A.
IC19
chosen
IC19 is a major Portuguese roadway linking Lisbon to the Sintra area and serving as one of the country’s busiest commuter routes.
-
B.
IC1
IC1 is a major Portuguese roadway that serves as an important inland north–south route connecting multiple regions and towns.
-
C.
IC15
IC15 is a Portuguese complementary itinerary road that forms part of the national IC (Itinerário Complementar) highway network.
-
D.
IC13
IC13 is a Portuguese complementary itinerary road that forms part of the national IC (Itinerário Complementar) highway network.
-
E.
IC16
IC16 is a Portuguese complementary itinerary road that forms part of the national IC (Itinerário Complementar) highway network.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1571fe76c8190a40b3679802a5475 |
completed | April 29, 2026, 12:56 a.m. |
Created at: April 16, 2026, 8:41 p.m.