Triple

T20703975
Position Surface form Disambiguated ID Type / Status
Subject South Carolina Ports Authority E508851 entity
Predicate shortName P43 FINISHED
Object SCPA 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: SCPA | Statement: [South Carolina Ports Authority, shortName, SCPA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SCPA
Context triple: [South Carolina Ports Authority, shortName, SCPA]
  • A. SCPA chosen
    SCPA is a New York State statute that governs procedures in the Surrogate’s Courts, primarily dealing with estates, wills, and related probate matters.
  • B. SCPC
    SCPC is the ICAO airport code assigned to Pucón Airport in Chile.
  • C. SCPO
    SCPO is the commonly used abbreviation for a Senior Chief Petty Officer, a senior enlisted rank in the U.S. Navy.
  • D. NSPA
    NSPA is the NATO Support and Procurement Agency, responsible for providing logistics, procurement, and support services to NATO member nations and partners.
  • E. LSCPA
    LSCPA is a public two-year community college in Port Arthur, Texas, offering academic transfer and workforce education programs as part of the Texas State University System.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c2b2a481909e31e9cb8f81ab55 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6c18dbda081908217dcb61cbf7ba4 completed April 21, 2026, 12:15 a.m.
Created at: April 16, 2026, 12:13 p.m.