Triple

T14370695
Position Surface form Disambiguated ID Type / Status
Subject Apple Calendar Server E356350 entity
Predicate supportsDirectoryService P203 FINISHED
Object LDAP E42572 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: LDAP | Statement: [Apple Calendar Server, supportsDirectoryService, LDAP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: LDAP
Context triple: [Apple Calendar Server, supportsDirectoryService, LDAP]
  • A. LDAP chosen
    LDAP (Lightweight Directory Access Protocol) is an open, standards-based protocol used to access and manage distributed directory information services over an IP network.
  • B. LDAPBIS
    LDAPBIS is an IETF working group responsible for revising and standardizing the Lightweight Directory Access Protocol (LDAP) specifications.
  • C. Active Directory
    Active Directory is Microsoft's centralized directory and identity management service used to authenticate and authorize users, computers, and resources in Windows-based networks.
  • D. ldapcompare
    ldapcompare is an OpenLDAP command-line utility used to compare attribute values of directory entries against specified values in an LDAP directory.
  • E. eDirectory
    eDirectory is Novell's enterprise directory service that provides a centralized, scalable repository for managing users, resources, and security across networks and applications.
  • 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_69d8279163a081908aec45c0e3f1e02f completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de8fb0b8988190ab834a85911c015c completed April 14, 2026, 7:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd4c5363a081909681b54c1d8218dc completed May 8, 2026, 2:37 a.m.
Created at: April 10, 2026, 1:15 a.m.