Triple
T37457963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life Tap |
E930845
|
entity |
| Predicate | classRestriction |
P175148
|
FINISHED |
| Object | Warlock only |
—
|
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: Warlock only | Statement: [Life Tap, classRestriction, Warlock only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classRestriction Context triple: [Life Tap, classRestriction, Warlock only]
-
A.
fieldRestriction
Indicates that access to or use of a particular field, area, or domain is limited or constrained by specified rules or conditions.
-
B.
restrictTo
chosen
Indicates that one entity limits or confines another entity’s scope, access, or applicability to a specified subset, condition, or context.
-
C.
restrictionProperty
Indicates a constraining characteristic or condition that limits or governs how another property or relationship may be applied or interpreted.
-
D.
policyRestriction
Indicates that an entity is subject to a limiting rule, condition, or constraint imposed by a policy.
-
E.
hasSemanticRestriction
Indicates that a concept or relation is constrained in meaning or usage by specific semantic conditions or limitations.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:17 p.m.