Triple
T28023632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organizational Unit |
E707752
|
entity |
| Predicate | distinguishedNameAttribute |
P82085
|
FINISHED |
| Object | ou |
—
|
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: ou | Statement: [Organizational Unit, distinguishedNameAttribute, ou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distinguishedNameAttribute Context triple: [Organizational Unit, distinguishedNameAttribute, ou]
-
A.
namingAuthorityContext
Indicates the authority or governing context under which an entity’s name is formally assigned or recognized.
-
B.
domainComponent
Indicates that one entity is a constituent or functional part of a larger domain or system represented by another entity.
-
C.
isDistinguishedBy
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
D.
logonName
Indicates the login identifier or username associated with an entity for authentication or access purposes.
-
E.
representedByAttribute
chosen
Indicates that one entity serves as an attribute-based representation or characterization of another entity.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 8:11 p.m.