Triple
T20210157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firewhisky |
E493467
|
entity |
| Predicate | inUniverseAgeRestriction |
P13299
|
FINISHED |
| Object | 17 |
—
|
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: 17 | Statement: [Firewhisky, inUniverseAgeRestriction, 17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseAgeRestriction Context triple: [Firewhisky, inUniverseAgeRestriction, 17]
-
A.
isAgeRestricted
Indicates that access to or use of something is limited based on the age of the person involved.
-
B.
hasAgeGuidelines
Indicates that there are specified age-related rules or recommendations governing how something should be accessed, used, or engaged with.
-
C.
ageRestrictionAppliedInSomeEditions
Indicates that age restrictions are enforced only in certain editions or versions of the work, not universally across all editions.
-
D.
inUniverseRestriction
Indicates that something is limited, applicable, or valid only within a specific fictional or defined universe or continuity.
-
E.
ageLimitAppliesAt
chosen
Indicates the specific age or point in time at which an age-related restriction or limit becomes effective for an 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed4706c81908a5e4a3023a9c22f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.