Triple
T28023657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Organizational Unit |
E707752
|
entity |
| Predicate | hasLDAPClassName |
P115320
|
FINISHED |
| Object | organizationalUnit |
—
|
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: organizationalUnit | Statement: [Organizational Unit, hasLDAPClassName, organizationalUnit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLDAPClassName Context triple: [Organizational Unit, hasLDAPClassName, organizationalUnit]
-
A.
hasLCClassification
Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
-
B.
namingAuthorityContext
Indicates the authority or governing context under which an entity’s name is formally assigned or recognized.
-
C.
hasCharacterClass
Indicates that an entity (such as a character) belongs to or is assigned a particular character class or role type.
-
D.
isAttributeClass
Indicates that one entity functions as a defining attribute or characteristic class for another entity.
-
E.
hasClassName
chosen
Indicates that an entity is associated with or identified by a specific class name in a classification or type system.
- 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_69f63c0ccf808190b7184694607fa98a |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:11 p.m.