Triple
T32526274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tube Neck |
E831322
|
entity |
| Predicate | inUniverseMortalityRate |
P4715
|
FINISHED |
| Object | extremely high |
—
|
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: extremely high | Statement: [Tube Neck, inUniverseMortalityRate, extremely high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseMortalityRate Context triple: [Tube Neck, inUniverseMortalityRate, extremely high]
-
A.
mortalityRate
chosen
Indicates the proportion of individuals in a defined population that die within a specified time period.
-
B.
inUniverseAge
Indicates the age of an entity as measured within the timeline or continuity of a specific fictional or defined universe.
-
C.
inUniverseRisk
Indicates that one entity poses a potential danger, threat, or harmful impact to another within a defined universe, context, or system.
-
D.
inUniverseCaliber
Indicates that something possesses a level of quality, power, or significance appropriate to or consistent with a particular fictional universe.
-
E.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another 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_69f34923e1548190be0524205d8cdf8f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:01 a.m.