Triple

T10174642
Position Surface form Disambiguated ID Type / Status
Subject RFC 974 E235818 entity
Predicate usesResourceRecordType P2554 FINISHED
Object MX 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: MX | Statement: [RFC 974, usesResourceRecordType, MX]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesResourceRecordType
Context triple: [RFC 974, usesResourceRecordType, MX]
  • A. hasRecordType chosen
    Indicates that an entity is associated with or classified under a specific type or category of record.
  • B. usesRoutingType
    Indicates that one entity employs or operates according to a specific routing type or routing method associated with another entity.
  • C. isResourceFor
    Indicates that one entity serves as a resource, support, or means of use for another entity.
  • D. hasTypeOfResource
    Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
  • E. usesNBAResources
    Indicates that an entity makes use of resources, materials, or services provided by the NBA.
  • 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_69ca84d1d5f88190ab878a1021ecff68 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdecd26a8c8190a391b9d5e47ebb72 completed April 2, 2026, 4:13 a.m.
PD Predicate disambiguation batch_69cd7c79f21c8190a7f31b2eab80b8ba completed April 1, 2026, 8:13 p.m.
Created at: March 30, 2026, 9:11 p.m.