Triple
T592294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robart |
E17301
|
entity |
| Predicate | hasUsageContext |
P5018
|
FINISHED |
| Object | personal identification |
—
|
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: personal identification | Statement: [Robart, hasUsageContext, personal identification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageContext Context triple: [Robart, hasUsageContext, personal identification]
-
A.
usedInMachineReadableContexts
Indicates that something is employed or applied within formats or environments that can be automatically processed and interpreted by machines.
-
B.
scopeOfUse
chosen
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
hasLanguageContext
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
-
D.
hasCountryContext
Indicates that something is associated with, interpreted within, or relevant to a specific country or national context.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bbaf53081908eed240bed09f63b |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.