Triple
T1097440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Social Security number |
E24300
|
entity |
| Predicate | uniqueness |
P9321
|
FINISHED |
| Object | intended to be unique per individual |
—
|
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: intended to be unique per individual | Statement: [Social Security number, uniqueness, intended to be unique per individual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueness Context triple: [Social Security number, uniqueness, intended to be unique per individual]
-
A.
uniqueClaim
Indicates that a claim is distinct and not duplicated or shared with any other claim in the given context.
-
B.
rarity
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
C.
distinction
Indicates that one entity is recognized, treated, or classified as different or separate from another.
-
D.
isUniqueWithinStandard
chosen
Indicates that an entity is the only one of its kind within the scope or constraints of a given standard or specification.
-
E.
nonExclusive
Indicates that the relationship or access is shared among multiple parties and is not limited to a single, exclusive holder.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9a1d3108190b2a304fef429848d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b745ef3481909a7ce4647c8567b3 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.