Triple
T33489574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Command Paper series |
E857701
|
entity |
| Predicate | usedByBody |
P171576
|
FINISHED |
| Object | UK Government |
—
|
NE NERFINISHED |
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: UK Government | Statement: [UK Command Paper series, usedByBody, UK Government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByBody Context triple: [UK Command Paper series, usedByBody, UK Government]
-
A.
usesBody
Indicates that one entity employs or utilizes the physical body of another (or its own) as a means or instrument to perform an action or function.
-
B.
usesBodyPart
Indicates that an entity performs an action or function by employing a specific body part as a means or tool.
-
C.
usedByFor
Indicates that one entity makes use of another entity for a specific purpose or function.
-
D.
adoptedByBodyOf
chosen
Indicates that a decision, document, or measure has been formally approved and accepted by a specific governing body or organization.
-
E.
usedByPerson
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 1, 2026, 1:38 a.m.