Triple
T27871954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oga Garra |
E704812
|
entity |
| Predicate | enforcesRules |
P113152
|
FINISHED |
| Object | through hired muscle |
—
|
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: through hired muscle | Statement: [Oga Garra, enforcesRules, through hired muscle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesRules Context triple: [Oga Garra, enforcesRules, through hired muscle]
-
A.
enforcesRule
chosen
Indicates that one entity compels or ensures that another entity follows or complies with a specified rule or set of rules.
-
B.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
C.
regulatingRules
Indicates that one entity establishes or enforces rules or standards that govern or control the behavior, operation, or conditions of another entity.
-
D.
enablesEnforcementOf
Indicates that one entity provides the authority, means, or conditions necessary for another entity to carry out enforcement actions or apply rules.
-
E.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 6:25 p.m.