Triple
T494777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior Lords of the Treasury |
E10268
|
entity |
| Predicate | formalFunction |
P14175
|
FINISHED |
| Object | subordinate Treasury minister |
—
|
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: subordinate Treasury minister | Statement: [Junior Lords of the Treasury, formalFunction, subordinate Treasury minister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formalFunction Context triple: [Junior Lords of the Treasury, formalFunction, subordinate Treasury minister]
-
A.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
B.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
C.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
D.
formed
Indicates that one entity came into existence, shape, or organization as a result of the actions or processes involving another entity.
-
E.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0fdd5608190815fa36485df8962 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebb2c908190960a4d0c014304cd |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.