Triple
T7845639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Separate Amenities Act |
E181915
|
entity |
| Predicate | affectedRight |
P17486
|
FINISHED |
| Object | freedom of movement |
—
|
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: freedom of movement | Statement: [Separate Amenities Act, affectedRight, freedom of movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedRight Context triple: [Separate Amenities Act, affectedRight, freedom of movement]
-
A.
hadRight
chosen
Indicates that an entity possessed a legal or moral entitlement to perform an action, access something, or claim something in relation to another entity or situation.
-
B.
affectedPerson
Indicates that a particular person is impacted or influenced by an event, action, or condition.
-
C.
affectedFunction
Indicates that one entity has an impact on, alters, or impairs the operation or behavior of another entity’s function.
-
D.
frontAffected
Indicates that an action, event, or condition primarily impacts the front side or front-facing part of an entity.
-
E.
affectedArea
Indicates the specific region or extent over which an event, condition, or influence has an impact.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb163d92fc8190a4efcb08d6b3d404 |
completed | March 31, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.