Triple
T32333475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LDAP syntax descriptions |
E826110
|
entity |
| Predicate | constrain |
P1050
|
FINISHED |
| Object | string representation of attribute values |
—
|
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: string representation of attribute values | Statement: [LDAP syntax descriptions, constrain, string representation of attribute values]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constrain Context triple: [LDAP syntax descriptions, constrain, string representation of attribute values]
-
A.
designedToConstrain
Indicates that one entity is intentionally created or configured to limit, restrict, or control the behavior, range, or properties of another entity.
-
B.
canConstrain
Indicates that one entity has the ability or authority to limit, restrict, or impose conditions on another entity or its behavior.
-
C.
constrainedBy
Indicates that one entity’s state, behavior, or possibilities are limited, restricted, or governed by another entity.
-
D.
usesConstriction
Indicates that one entity applies pressure by tightening or squeezing around another entity to restrain, control, or affect it.
-
E.
restriction
chosen
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:47 a.m.