Triple
T25704047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glubbdubdrib |
E644538
|
entity |
| Predicate | notableAbilityOfInhabitants |
P182808
|
FINISHED |
| Object | raising the dead |
—
|
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: raising the dead | Statement: [Glubbdubdrib, notableAbilityOfInhabitants, raising the dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAbilityOfInhabitants Context triple: [Glubbdubdrib, notableAbilityOfInhabitants, raising the dead]
-
A.
inhabitantAbility
chosen
Indicates that an inhabitant possesses a particular capability, skill, or power.
-
B.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
C.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
D.
mainInhabitant
Indicates that an entity is the primary or most significant resident or occupant of a particular place or location.
-
E.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 21, 2026, 9 p.m.