Triple
T640294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parliament Acts 1911 and 1949 |
E16722
|
entity |
| Predicate | hasBeenInvokedIn |
P8581
|
FINISHED |
| Object | enactment of the Parliament Act 1949 |
—
|
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: enactment of the Parliament Act 1949 | Statement: [Parliament Acts 1911 and 1949, hasBeenInvokedIn, enactment of the Parliament Act 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenInvokedIn Context triple: [Parliament Acts 1911 and 1949, hasBeenInvokedIn, enactment of the Parliament Act 1949]
-
A.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
B.
hasBeenDeclaredFor
Indicates that an entity has been officially announced, designated, or proclaimed for a particular purpose, status, or context.
-
C.
usedToBeCalled
Indicates that an entity previously had a different name or title than the one it currently has.
-
D.
isReferencedIn
chosen
Indicates that one entity is cited, mentioned, or otherwise referred to within another entity.
-
E.
calledBy
Indicates that one entity initiates a call or invocation to 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49f0189b08190a584b744f36fa761 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0830008190a26ee158ed4dd1fe |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.