Triple
T38588962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Professor Putricide |
E932408
|
entity |
| Predicate | requiresPrecedingBoss |
P202441
|
FINISHED |
| Object | Festergut |
—
|
NE NERFINISHED |
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: Festergut | Statement: [Professor Putricide, requiresPrecedingBoss, Festergut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPrecedingBoss Context triple: [Professor Putricide, requiresPrecedingBoss, Festergut]
-
A.
isBeforeBoss
Indicates that one entity holds a position or rank that is subordinate to, or comes earlier in hierarchy than, another entity designated as the boss.
-
B.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
C.
isAfterBoss
Indicates that one entity occurs or is positioned later in sequence or time than the boss entity.
-
D.
requiresBossFight
chosen
Indicates that completing or progressing past a certain point necessitates defeating a designated boss character in combat.
-
E.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: May 3, 2026, 4:32 p.m.