Triple
T14311733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanna v. Plumer |
E354848
|
entity |
| Predicate | rulesEnablingAct |
P113718
|
FINISHED |
| Object | interpreted |
—
|
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: interpreted | Statement: [Hanna v. Plumer, rulesEnablingAct, interpreted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesEnablingAct Context triple: [Hanna v. Plumer, rulesEnablingAct, interpreted]
-
A.
authorizationAct
Indicates that an entity formally grants permission or legal authority for another entity to perform a specific action or set of actions.
-
B.
implementsAct
Indicates that one entity carries out, executes, or puts into effect a specified act, plan, or directive associated with another entity.
-
C.
definesAct
Indicates that one entity specifies, determines, or lays out the nature, scope, or details of an action performed by another entity.
-
D.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
E.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b386d0819087d14f3ce84a1997 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e07d1f88190bdcd20967e484718 |
completed | April 14, 2026, 12:07 p.m. |
Created at: April 10, 2026, 1:12 a.m.