Triple
T17147095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Cebu |
E416117
|
entity |
| Predicate | managesTrafficType |
P621
|
FINISHED |
| Object | domestic cargo |
—
|
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: domestic cargo | Statement: [Port of Cebu, managesTrafficType, domestic cargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesTrafficType Context triple: [Port of Cebu, managesTrafficType, domestic cargo]
-
A.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
B.
hasTrafficManagement
Indicates that an entity implements, uses, or is associated with systems or measures for controlling and optimizing traffic flow.
-
C.
trafficManagementStrategy
Indicates a method or plan used to control, organize, or optimize the flow of traffic within a transportation system.
-
D.
trafficManagementGoal
Indicates a goal or objective related to managing, regulating, or optimizing traffic flow and conditions.
-
E.
trafficType
chosen
Indicates the category or nature of traffic involved in a given interaction, flow, or connection (e.g., type of network, data, or transport traffic).
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2db20d48190b5d69ccf89f3bc42 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.