Triple
T5630744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Sea Ports Authority |
E147823
|
entity |
| Predicate | typeOfPortAuthority |
P10788
|
FINISHED |
| Object | seaport authority |
—
|
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: seaport authority | Statement: [Red Sea Ports Authority, typeOfPortAuthority, seaport authority]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPortAuthority Context triple: [Red Sea Ports Authority, typeOfPortAuthority, seaport authority]
-
A.
typeOfPortFacility
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
B.
hasTransportAuthority
Indicates that one entity holds official power or responsibility to manage, regulate, or oversee transportation services or infrastructure for another entity or area.
-
C.
hasPublicAuthorityType
chosen
Indicates that an entity possesses a specific type or category of public authority status or role.
-
D.
legalAuthorityType
Indicates the specific kind or category of legal authority that governs, authorizes, or regulates an entity or action.
-
E.
governsOfficeType
Indicates that an entity has authoritative control or regulatory oversight over a particular type or category of office.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225cdcdc819095034f12c39ef755 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.