Triple
T8552029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyper Neo Geo 64 |
E202465
|
entity |
| Predicate | lifespanDescription |
P585
|
FINISHED |
| Object | short-lived |
—
|
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: short-lived | Statement: [Hyper Neo Geo 64, lifespanDescription, short-lived]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifespanDescription Context triple: [Hyper Neo Geo 64, lifespanDescription, short-lived]
-
A.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
B.
lifespanType
Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined duration.
-
C.
lifePeriod
Indicates the span of time during which an entity exists, is active, or is valid.
-
D.
lifetimeInGenerations
Indicates the number of successive generations over which something (e.g., an effect, trait, or validity) persists or remains applicable.
-
E.
supportsLifespan
Indicates that one entity contributes to maintaining, extending, or enabling the full duration of another entity’s life or functional existence.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe886fb788190a73e7c76c4f86409 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.