Triple

T23113489
Position Surface form Disambiguated ID Type / Status
Subject AFAS E576384 entity
Predicate abbreviation P43 FINISHED
Object AFAS 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: AFAS | Statement: [AFAS, abbreviation, AFAS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: AFAS
Context triple: [AFAS, abbreviation, AFAS]
  • A. AFAS
    AFAS is a regional agreement among ASEAN member states aimed at progressively liberalizing trade in services to enhance economic integration and competitiveness in Southeast Asia.
  • B. AFAS Live
    AFAS Live is a major indoor music and events venue in Amsterdam, Netherlands, known for hosting concerts, shows, and large-scale entertainment performances.
  • C. AFAS Software chosen
    AFAS Software is a Dutch company that develops business and accounting software solutions for organizations in various sectors.
  • D. AFS
    AFS is an abbreviation commonly used for the Auxiliary Fire Service, a volunteer civil defense firefighting organization that supported regular fire brigades, particularly during wartime.
  • E. AFS
    AFS is the National Rail station code for Ashford (Surrey) railway station in 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_69e245f4af548190898d434a64a1e774 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e1121c08190a1d29fe594071c46 completed April 29, 2026, 4:50 a.m.
Created at: April 17, 2026, 3:58 p.m.