Triple

T9865264
Position Surface form Disambiguated ID Type / Status
Subject RFC 4514 E239815 entity
Predicate basedOn P98 FINISHED
Object X.500 Distinguished Name model E233829 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: X.500 Distinguished Name model | Statement: [RFC 4514, basedOn, X.500 Distinguished Name model]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: X.500 Distinguished Name model
Context triple: [RFC 4514, basedOn, X.500 Distinguished Name model]
  • A. X.500 chosen
    X.500 is an ITU-T and ISO/IEC standard series that defines a directory service model and protocols for distributed, hierarchical storage and retrieval of information about networked entities.
  • B. RFC 4513
    RFC 4513 is an IETF standard that specifies authentication methods and security mechanisms for the Lightweight Directory Access Protocol (LDAP).
  • C. RFC 4519
    RFC 4519 is an IETF specification that defines a standard set of schema attributes and object classes for use in LDAP directories.
  • D. RFC 4518
    RFC 4518 is an Internet standard that specifies string preparation and comparison rules for use in LDAP directories.
  • E. RFC 4514
    RFC 4514 is an IETF standard that specifies the string representation of Distinguished Names in the Lightweight Directory Access Protocol (LDAP).
  • 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_69ca84e7506c819095cbde4ff16512bb completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb3ba7f288190a15ebec2cc3112c4 completed April 2, 2026, 12:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1e44dc0b8819082294a479299814e completed April 5, 2026, 4:25 a.m.
Created at: March 30, 2026, 8:36 p.m.