Triple
T1207303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GPO |
E25917
|
entity |
| Predicate | technologyRole |
P24646
|
FINISHED |
| Object | provides digital access to government information |
—
|
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: provides digital access to government information | Statement: [GPO, technologyRole, provides digital access to government information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyRole Context triple: [GPO, technologyRole, provides digital access to government information]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
developmentRole
Indicates that an entity participates in the creation, design, or production of another entity in a specific developmental capacity or function.
-
C.
developerOfWork
Indicates that one entity is the creator or producer responsible for making or developing a particular work.
-
D.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
E.
technologyField
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc483b481908e5bfef5d2f4fc5a |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:46 p.m.