Triple
T12927613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USM Auriga |
E309283
|
entity |
| Predicate | consequenceOfExperiments |
P107066
|
FINISHED |
| Object | xenomorph outbreak |
—
|
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: xenomorph outbreak | Statement: [USM Auriga, consequenceOfExperiments, xenomorph outbreak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consequenceOfExperiments Context triple: [USM Auriga, consequenceOfExperiments, xenomorph outbreak]
-
A.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
-
B.
notableExperiment
Indicates that an entity is recognized for having conducted or been the subject of a particularly important or influential experiment.
-
C.
historicalExperiment
Indicates that an experiment was conducted in the past and is of historical significance or relevance.
-
D.
majorExperiment
Indicates that an entity conducts or is involved in a primary, large-scale, or most significant experiment in a given context.
-
E.
hasConsequenceHypothesis
Indicates that one situation, event, or statement is hypothesized to lead to or imply a particular consequence.
- F. None of above. chosen
Provenance (4 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_69d7bdfa933c8190b5a27aa4a08a19b7 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971ec72a48190aceef10630603d2c |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fab4d0881909a7a4d66bab9aa85 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d970f6f5748190ad35aff801db53d5 |
completed | April 10, 2026, 9:51 p.m. |
Created at: April 9, 2026, 5:42 p.m.