Triple

T4115498
Position Surface form Disambiguated ID Type / Status
Subject Norfolk International Terminals E90279 entity
Predicate isStrategicNodeIn P20548 FINISHED
Object global supply chains 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: global supply chains | Statement: [Norfolk International Terminals, isStrategicNodeIn, global supply chains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isStrategicNodeIn
Context triple: [Norfolk International Terminals, isStrategicNodeIn, global supply chains]
  • A. isKeyNodeIn chosen
    Indicates that a node serves as a primary or critical element within a specified structure, system, or context.
  • B. hasStrategicPass
    Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
  • C. hasStrategicFunction
    Indicates that an entity serves a planned, goal-oriented role or purpose within a broader strategy or system.
  • D. 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.
  • E. isNucleusOf
    Indicates that one entity functions as the central or most important core component of 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_69aed95c080881908125e30c5dcdc6f8 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af03d7240c8190a64dcbc669772808 completed March 9, 2026, 5:31 p.m.
PD Predicate disambiguation batch_69af0183eb84819087d7184de28f5514 completed March 9, 2026, 5:21 p.m.
Created at: March 9, 2026, 3:41 p.m.