Triple
T29082968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godslayer sword |
E734026
|
entity |
| Predicate | primaryUserOccupation |
P180169
|
FINISHED |
| Object | assassin |
—
|
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: assassin | Statement: [Godslayer sword, primaryUserOccupation, assassin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUserOccupation Context triple: [Godslayer sword, primaryUserOccupation, assassin]
-
A.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
B.
mainOccupationFrom
Indicates that the specified occupation is the primary or main job held by the given entity.
-
C.
natureOfOccupation
Indicates the type or character of a person's occupation, describing what kind of work or role it is rather than who performs it.
-
D.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
-
E.
ownerProfession
chosen
Indicates that the profession or occupation is associated with, or held by, the owner of a specified 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
Created at: April 28, 2026, 10:57 a.m.