Triple
T1086578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HAV |
E24064
|
entity |
| Predicate | terminal3Role |
P5518
|
FINISHED |
| Object | main international terminal |
—
|
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: main international terminal | Statement: [HAV, terminal3Role, main international terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminal3Role Context triple: [HAV, terminal3Role, main international terminal]
-
A.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
B.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
D.
terminalArea
Indicates that one entity is a designated terminal area or zone associated with another entity (such as a facility, system, or region).
-
E.
servesTerminal
Indicates that one entity functions as a terminal or endpoint facility that is served or operated by another entity.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b963161081908a523c8d63871652 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.