Triple

T14322288
Position Surface form Disambiguated ID Type / Status
Subject Afilias E355120 entity
Predicate operates P24 FINISHED
Object .info E771982 NE 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: .info | Statement: [Afilias, operates, .info]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: .info
Context triple: [Afilias, operates, .info]
  • A. .info chosen
    .info is a generic top-level domain (gTLD) commonly used for informational websites on the internet.
  • B. EInfo
    EInfo is an NCBI E-utilities endpoint that provides metadata and field information about a specific NCBI database.
  • C. IN
    IN is the two-letter ISO 3166-1 alpha-2 country code representing India in international standards and systems.
  • D. IN
    IN is the official two-letter United States Postal Service abbreviation for the state of Indiana.
  • E. IN
    IN is the commonly used abbreviation for the Innocence Network, a coalition of organizations dedicated to exonerating wrongfully convicted individuals and reforming the criminal justice system.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8278ed42c8190b9f882dcce611347 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de883d1de88190a1e2bf2f1b692197 completed April 14, 2026, 6:32 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd468e263c81909d7261bcfd949579 completed May 8, 2026, 2:12 a.m.
Created at: April 10, 2026, 1:13 a.m.