Triple
T38218993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chestburster |
E1010757
|
entity |
| Predicate | methodOfEmergence |
P122523
|
FINISHED |
| Object | Bursts from host chest |
—
|
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: Bursts from host chest | Statement: [Chestburster, methodOfEmergence, Bursts from host chest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfEmergence Context triple: [Chestburster, methodOfEmergence, Bursts from host chest]
-
A.
modeOfEmergence
chosen
Indicates the manner or process through which something comes into existence, develops, or arises.
-
B.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
C.
emergesAt
Indicates that something comes into existence, becomes visible, or starts to be apparent at a specific time, place, or condition.
-
D.
methodOfResurrection
Indicates the specific process or means by which an entity is brought back to life or restored from death.
-
E.
emergesAs
Indicates that one entity comes to be recognized, develops, or appears in the role, form, or status of another entity over time.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.