Triple
T35932970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qatar Fertiliser Company |
E1039215
|
entity |
| Predicate | exportTerminal |
P184241
|
FINISHED |
| Object | Mesaieed Port |
—
|
NE NERFINISHED |
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: Mesaieed Port | Statement: [Qatar Fertiliser Company, exportTerminal, Mesaieed Port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exportTerminal Context triple: [Qatar Fertiliser Company, exportTerminal, Mesaieed Port]
-
A.
usedTerminal
Indicates that an entity made use of or interacted with a particular terminal or endpoint device.
-
B.
terminalFunction
Indicates that an entity serves as an endpoint or final functional unit within a larger structure, process, or system.
-
C.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
D.
TerminalEUsedFor
Indicates that a terminal E is used for a particular purpose, function, or activity.
-
E.
terminal3Use
Indicates that an entity makes use of or operates from terminal 3 (such as a specific terminal in a facility, station, or airport).
- 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_69f76e23e4688190a5369138755138bf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7ac2210e481909279dade5328825c |
completed | May 3, 2026, 8:12 p.m. |
Created at: May 3, 2026, 4:07 p.m.