Triple
T32333502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDAP syntax descriptions |
E826110
|
entity |
| Predicate | mustBeUniquePer |
P38254
|
FINISHED |
| Object | OID within a schema |
—
|
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: OID within a schema | Statement: [LDAP syntax descriptions, mustBeUniquePer, OID within a schema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mustBeUniquePer Context triple: [LDAP syntax descriptions, mustBeUniquePer, OID within a schema]
-
A.
uniquenessCondition
chosen
Indicates that a specified element, value, or combination of attributes must be unique within a given set, context, or domain, with no duplicates allowed.
-
B.
isUniqueTo
Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
-
C.
hasUniqueness
Indicates that something possesses a distinctive or one-of-a-kind quality that sets it apart from others.
-
D.
typeOfUniqueness
Indicates that one entity’s uniqueness is characterized, classified, or constrained by the specific kind or mode of uniqueness associated with another entity.
-
E.
membershipUniqueness
Indicates that each member in a given context is uniquely associated with a single group, role, or collection, preventing duplicate or overlapping memberships.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be155a10819082fa30e9b235aee9 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:47 a.m.