Triple
T22337058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WGNQ-CD |
E552177
|
entity |
| Predicate | digital |
P147824
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [WGNQ-CD, digital, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digital Context triple: [WGNQ-CD, digital, yes]
-
A.
digitalByDefault
Indicates that the primary or standard method for performing the related process, service, or interaction is through digital channels rather than physical or manual means.
-
B.
digitalRelease
Indicates that a work is made available to the public through digital or online distribution channels.
-
C.
digitalSignal
Indicates that the relationship or action involves representing, transmitting, or processing information as a discrete-time, discrete-value (digital) signal between entities.
-
D.
digitalProduct
Indicates that one entity is a product that exists in digital form or is delivered electronically rather than physically.
-
E.
digitalProvider
Indicates that one entity serves as the supplier or source of digital services, content, or infrastructure for another entity.
- F. None of above. chosen
Provenance (4 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157804e60819094e2a903ace6f4b2 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.