Triple
T10360603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4519 |
E244122
|
entity |
| Predicate | protocolAbbreviation |
P43
|
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: [RFC 4519, protocolAbbreviation, LDAP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LDAP Context triple: [RFC 4519, protocolAbbreviation, 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9609c4481908b7d72ecf1adaa73 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7953205cc8190ad7f28a7436049bc |
completed | April 9, 2026, 12:01 p.m. |
Created at: April 6, 2026, 11:59 a.m.