Triple
T11790301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haifa Port |
E280369
|
entity |
| Predicate | hasContainerTerminal |
P101593
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Haifa Port, hasContainerTerminal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContainerTerminal Context triple: [Haifa Port, hasContainerTerminal, true]
-
A.
hasCargoTerminal
Indicates that a location or facility includes or is equipped with a cargo terminal for handling freight.
-
B.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
C.
hasPassengerTerminalFunction
Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
-
D.
hasTerminalFacility
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
-
E.
hasDomesticTerminal
Indicates that a transportation facility, typically an airport, includes a terminal dedicated to domestic (within-country) travel operations.
- F. None of above. chosen
Provenance (4 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a587c2d881909297c3a6c7d26080 |
completed | April 10, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.