Triple
T19606854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitzana terminal |
E470627
|
entity |
| Predicate | trafficPriority |
P57692
|
FINISHED |
| Object | goods |
—
|
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: goods | Statement: [Nitzana terminal, trafficPriority, goods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficPriority Context triple: [Nitzana terminal, trafficPriority, goods]
-
A.
transportPriority
chosen
Indicates that one entity is assigned a higher or specific level of precedence over others in being transported or moved.
-
B.
trafficLevel
Indicates the degree of congestion or flow intensity present in a transportation network or route at a given time.
-
C.
trafficDirection
Indicates the direction in which traffic is intended or allowed to move relative to a given reference point or segment.
-
D.
roadTraffic
Indicates the presence, flow, or conditions of vehicles and movement along roads or streets.
-
E.
relativeTrafficLevel
Indicates the comparative intensity or volume of traffic between two or more locations, routes, or time periods.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640c8aae8819086337e364724f1cb |
completed | April 20, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69e514e166dc8190a0f147e0b4c8bbe7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.