Triple
T18298620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halo (ringworld) |
E438296
|
entity |
| Predicate | activationEffect |
P1634
|
FINISHED |
| Object | kills sentient life within its effective radius |
—
|
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: kills sentient life within its effective radius | Statement: [Halo (ringworld), activationEffect, kills sentient life within its effective radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationEffect Context triple: [Halo (ringworld), activationEffect, kills sentient life within its effective radius]
-
A.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
B.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
C.
primaryEffect
chosen
Indicates the main direct outcome or consequence that results from a given cause, action, or condition.
-
D.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
E.
activationProperty
Indicates a relationship where one entity specifies the conditions, parameters, or characteristics that determine how another entity becomes active or is triggered.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017d96588190ac1e326803142976 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.