Triple
T84328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Deputies |
E1696
|
entity |
| Predicate | orderOfDeputies |
P3458
|
FINISHED |
| Object | clerical order |
—
|
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: clerical order | Statement: [House of Deputies, orderOfDeputies, clerical order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderOfDeputies Context triple: [House of Deputies, orderOfDeputies, clerical order]
-
A.
ordinalInOffice
Indicates the numerical order or rank of an individual’s term or tenure in a particular office or position.
-
B.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
C.
hasNumberOfCouncillors
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
D.
presidingOfficerForCount
Indicates that a particular officer has official responsibility for overseeing or presiding over a specific count (such as a charge, claim, or item) within a legal or procedural context.
-
E.
electsDelegatesTo
Indicates that one entity selects or votes to choose representatives (delegates) who will act or decide on its behalf in another body or process.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24f4e73c081908d2da146226ef05e |
completed | Feb. 28, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69a24eb469548190b38c24e81f36c838 |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a24f4b4658819087902414959161fb |
completed | Feb. 28, 2026, 2:13 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.