Triple
T149234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts of Parliament |
E3395
|
entity |
| Predicate | createdByProcess |
P924
|
FINISHED |
| Object | legislative process |
—
|
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: legislative process | Statement: [Acts of Parliament, createdByProcess, legislative process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByProcess Context triple: [Acts of Parliament, createdByProcess, legislative process]
-
A.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
B.
usedProcess
chosen
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
C.
createdByAct
Indicates that something came into existence or was produced as the result of a specific act or action.
-
D.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
E.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
- 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_69a252868de4819080e21c9938bfe8b6 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2580ca15481909fa3e87d804a1b23 |
completed | Feb. 28, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69a256599db08190a7b000b381d32ec4 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.