Triple
T35281453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub 37 |
E1018942
|
entity |
| Predicate | hasDigitalControl |
P199492
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sub 37, hasDigitalControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalControl Context triple: [Sub 37, hasDigitalControl, true]
-
A.
hasDigitalSystem
Indicates that an entity possesses, uses, or is equipped with a digital system (such as software, hardware, or an integrated digital platform).
-
B.
hasDigitalSignal
Indicates that an entity possesses, carries, or is associated with a digital (discrete-valued) signal.
-
C.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
D.
hasDigitalDivision
Indicates that one entity is divided into parts or segments within a digital or electronic context by another entity or according to a specified digital scheme.
-
E.
hasAnalog
Indicates that one entity corresponds to or functions similarly to another entity in a comparable context or role.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
| PDg | Predicate description generation | batch_69ff3e16527c81908c8d89da704ce012 |
completed | May 9, 2026, 2 p.m. |
Created at: May 3, 2026, 4:03 p.m.