Triple
T13241397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunting Act 2004 |
E315287
|
entity |
| Predicate | wasHeldToBe |
P108682
|
FINISHED |
| Object | valid primary legislation |
—
|
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: valid primary legislation | Statement: [Hunting Act 2004, wasHeldToBe, valid primary legislation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasHeldToBe Context triple: [Hunting Act 2004, wasHeldToBe, valid primary legislation]
-
A.
oftenHeldToBe
Indicates that something is frequently regarded, considered, or believed to be a certain way by many people or in many contexts.
-
B.
wasHeldUnder
Indicates that an event, activity, or state took place while being subject to the authority, control, jurisdiction, or auspices of a particular entity or condition.
-
C.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
D.
heldThat
Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
-
E.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:23 p.m.