Triple
T36096131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forster Act |
E1044066
|
entity |
| Predicate | madePossible |
P12716
|
FINISHED |
| Object | compulsory attendance by by-laws |
—
|
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: compulsory attendance by by-laws | Statement: [Forster Act, madePossible, compulsory attendance by by-laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madePossible Context triple: [Forster Act, madePossible, compulsory attendance by by-laws]
-
A.
possiblyBy
Indicates that an action, creation, or effect may have been caused or produced by a particular entity, but this attribution is uncertain or not definitively established.
-
B.
madeTo
Indicates that one entity is created, produced, or constructed for the purpose, use, or benefit of another entity.
-
C.
canMake
Indicates that one entity has the ability or capacity to create, produce, or assemble another entity.
-
D.
maySucceed
Indicates that one entity has the potential or possibility to follow or replace another in a role, position, or sequence.
-
E.
mayResultIn
chosen
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
- 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.