Triple
T35405015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEI |
E1023341
|
entity |
| Predicate | uniquePer |
P38254
|
FINISHED |
| Object | registered entity |
—
|
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: registered entity | Statement: [UEI, uniquePer, registered entity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniquePer Context triple: [UEI, uniquePer, registered entity]
-
A.
uniqueUpTo
Indicates that one entity is determined uniquely by another, except for differences within a specified equivalence or tolerance (i.e., unique modulo that relation).
-
B.
typeOfUniqueness
Indicates that one entity’s uniqueness is characterized, classified, or constrained by the specific kind or mode of uniqueness associated with another entity.
-
C.
isUniqueTo
Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
-
D.
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.
-
E.
uniqueAspect
Indicates that the subject possesses a distinctive feature or characteristic that sets it apart from others.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79540f4488190957f5abf736f437f |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.