Triple
T27857598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LASPO 2012 |
E704129
|
entity |
| Predicate | removedFromScope |
P16758
|
FINISHED |
| Object | most employment law legal aid |
—
|
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: most employment law legal aid | Statement: [LASPO 2012, removedFromScope, most employment law legal aid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromScope Context triple: [LASPO 2012, removedFromScope, most employment law legal aid]
-
A.
removedFrom
chosen
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
B.
removedAfter
Indicates that one entity is removed or deleted at a point in time that occurs after the removal or deletion of another entity.
-
C.
removedBefore
Indicates that one entity was removed or taken away earlier in time than another specified entity or event.
-
D.
removedControlFrom
Indicates that one entity has taken away or revoked another entity’s authority, power, or control over something.
-
E.
laterRemovedTo
Indicates that an entity was moved or transferred to a location or state at a later time, after an earlier condition or placement.
- 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_69ef840e614c8190a88cf9638c14a265 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:15 p.m.