Triple
T27214500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavin (The Walking Dead) |
E684098
|
entity |
| Predicate | enforcesRulesOf |
P108402
|
FINISHED |
| Object | Savior protection racket system |
—
|
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: Savior protection racket system | Statement: [Gavin (The Walking Dead), enforcesRulesOf, Savior protection racket system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcesRulesOf Context triple: [Gavin (The Walking Dead), enforcesRulesOf, Savior protection racket system]
-
A.
enforcesRule
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
chosen
Indicates that one entity establishes or enforces rules or standards that govern or control the behavior, operation, or conditions of another entity.
-
D.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
E.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 9:40 a.m.