Triple
T9761626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSSet |
E236683
|
entity |
| Predicate | elementUniqueness |
P38254
|
FINISHED |
| Object | uniqueElements |
—
|
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: uniqueElements | Statement: [NSSet, elementUniqueness, uniqueElements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elementUniqueness Context triple: [NSSet, elementUniqueness, uniqueElements]
-
A.
typeOfUniqueness
Indicates that one entity’s uniqueness is characterized, classified, or constrained by the specific kind or mode of uniqueness associated with another entity.
-
B.
isUniqueTo
Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
-
C.
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.
-
D.
isUniqueWithinSystem
Indicates that an entity exists only once and has no duplicates within the defined system or scope.
-
E.
isUniqueWithinStandard
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda04c70108190a8ed09eb6f2a124e |
completed | April 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:25 p.m.