Triple
T32514037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahasapeemapetilon |
E831011
|
entity |
| Predicate | usedForCharacterOccupation |
P186977
|
FINISHED |
| Object | convenience store owner |
—
|
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: convenience store owner | Statement: [Nahasapeemapetilon, usedForCharacterOccupation, convenience store owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForCharacterOccupation Context triple: [Nahasapeemapetilon, usedForCharacterOccupation, convenience store owner]
-
A.
basedOnCharacterOccupation
Indicates that something is derived from, inspired by, or determined according to a character’s occupation or job role.
-
B.
allowedOccupationOf
Indicates that one entity is permitted or authorized to hold or perform the occupation associated with another entity.
-
C.
usedForCharacterType
Indicates that something is intended to be used for, or is suitable for, a particular type of character.
-
D.
settingOfCharacterOccupation
Indicates the place or environment in which a character performs or holds their occupation.
-
E.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 1, 2026, 1 a.m.