Triple
T37629563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mdina |
E936302
|
entity |
| Predicate | trafficPolicy |
P29930
|
FINISHED |
| Object | largely car-free |
—
|
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: largely car-free | Statement: [Mdina, trafficPolicy, largely car-free]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trafficPolicy Context triple: [Mdina, trafficPolicy, largely car-free]
-
A.
transportPolicy
Indicates a relationship where an authority or organization defines rules, strategies, or guidelines governing how transportation systems are planned, operated, or regulated.
-
B.
trackingPolicy
Indicates a relationship where one party defines or applies rules governing how another party’s activities, data, or movements are monitored and recorded.
-
C.
trafficManagementStrategy
Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
-
D.
dstPolicy
Indicates a policy or rule that governs how actions, traffic, or effects are applied to a destination entity.
-
E.
trafficRestriction
chosen
Indicates a limitation or prohibition on the movement or flow of traffic between entities, such as vehicles, routes, or areas.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.