Triple
T20190209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metroid (organism) |
E492961
|
entity |
| Predicate | fictionalPurpose |
P112894
|
FINISHED |
| Object | biological weapon |
—
|
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: biological weapon | Statement: [Metroid (organism), fictionalPurpose, biological weapon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalPurpose Context triple: [Metroid (organism), fictionalPurpose, biological weapon]
-
A.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
B.
fictionalFocus
Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
-
C.
fictionalContent
Indicates that one entity is content whose subject matter, events, or characters are imaginary or invented rather than factual.
-
D.
designedPurposeInFiction
chosen
Indicates that something is intentionally created within a fictional context to serve a particular role, function, or narrative purpose.
-
E.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad4d7a88190b70dfb74a2daafba |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.