Triple
T34253825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coercion Act 1881 |
E878816
|
entity |
| Predicate | legalAllows |
P199768
|
FINISHED |
| Object | detention without trial |
—
|
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: detention without trial | Statement: [Coercion Act 1881, legalAllows, detention without trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalAllows Context triple: [Coercion Act 1881, legalAllows, detention without trial]
-
A.
licenseAllows
Indicates that a particular license grants permission for a specified action, use, or access involving an entity.
-
B.
languageAllowance
Indicates the extent to which one entity permits or supports the use of a particular language by another entity.
-
C.
legalIn
Indicates that an action, status, or entity is permitted or valid under the laws or regulations of a specified jurisdiction.
-
D.
legalLicenseIn
Indicates that an entity holds a valid legal license or authorization to operate, practice, or conduct a specified activity within a particular jurisdiction or region.
-
E.
hasAllowedUse
Indicates that one entity is permitted to use, access, or otherwise make use of another entity under defined conditions or rules.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
| PDg | Predicate description generation | batch_69ff56edc4d081908f1d263e05cbd512 |
completed | May 9, 2026, 3:46 p.m. |
Created at: May 1, 2026, 1:56 a.m.