Triple
T16747081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSAP |
E406983
|
entity |
| Predicate | exampleValueUsage |
P83556
|
FINISHED |
| Object | SNAP extension |
—
|
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: SNAP extension | Statement: [DSAP, exampleValueUsage, SNAP extension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exampleValueUsage Context triple: [DSAP, exampleValueUsage, SNAP extension]
-
A.
valueExample
chosen
Indicates that something is provided as an illustrative or sample instance of a particular value.
-
B.
valueFormatExample
Indicates an example of how a value should be formatted or represented.
-
C.
usageType
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
usedAsExampleIn
Indicates that one entity is cited or presented as an illustrative example within another entity, such as a text, discussion, or explanation.
-
E.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2311748190a17416de577ad159 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.