Triple

T22195280
Position Surface form Disambiguated ID Type / Status
Subject FSCT E548530 entity
Predicate hasAcronym P43 FINISHED
Object FSCT 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: FSCT | Statement: [FSCT, hasAcronym, FSCT]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FSCT
Context triple: [FSCT, hasAcronym, FSCT]
  • A. FSCT chosen
    FSCT is the acronym for the Field Security Coordination Team, a group responsible for organizing and overseeing security measures in field operations.
  • B. FCT
    FCT is the commonly used abbreviation for FC Twente, a professional football club based in Enschede, Netherlands.
  • C. FCT
    FCT is the common abbreviation for FC Tulsa, a professional soccer club based in Tulsa, Oklahoma.
  • D. FCT
    FCT is the Federal Capital Territory of Nigeria, encompassing the planned city of Abuja and serving as the nation’s administrative and political center.
  • E. FST
    FST is the three-letter National Rail station code for London’s Fenchurch Street railway station, a central terminus serving commuter routes in the east of England.
  • 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_69e11e3ecc7c8190b5f94cd8f42e9d37 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12ae6f7a881908cf1772326f91467 completed April 28, 2026, 9:47 p.m.
Created at: April 16, 2026, 8:35 p.m.