Triple
T20101717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Al Hudaydah |
E496558
|
entity |
| Predicate | isCriticalNodeIn |
P20548
|
FINISHED |
| Object | Yemen’s supply chain |
—
|
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: Yemen’s supply chain | Statement: [Port of Al Hudaydah, isCriticalNodeIn, Yemen’s supply chain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCriticalNodeIn Context triple: [Port of Al Hudaydah, isCriticalNodeIn, Yemen’s supply chain]
-
A.
isKeyNodeIn
chosen
Indicates that a node serves as a primary or critical element within a specified structure, system, or context.
-
B.
isMajorNodeOf
Indicates that one node serves as a primary or central node within, or in relation to, another structure, network, or system.
-
C.
isEssentialLinkFor
Indicates that one entity serves as a necessary or critical connection enabling or supporting another entity or process.
-
D.
isNucleusOf
Indicates that one entity functions as the central or most important core component of another entity.
-
E.
isCentralTo
Indicates that something plays a primary, essential, or defining role in relation to something else, such that the latter depends on or is organized around it.
- 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_69da626eee3881909f3454986d4a6511 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66670a5b48190afe06c8a582bba3d |
completed | April 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:27 p.m.