Triple
T29050809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth (Marvel Cinematic Universe) |
E735256
|
entity |
| Predicate | hasBlipDuration |
P154713
|
FINISHED |
| Object | 5 years |
—
|
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: 5 years | Statement: [Earth (Marvel Cinematic Universe), hasBlipDuration, 5 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlipDuration Context triple: [Earth (Marvel Cinematic Universe), hasBlipDuration, 5 years]
-
A.
hasDurationCharacteristic
chosen
Indicates that something possesses a specific temporal property, such as length, span, or persistence over time.
-
B.
hasDurationType
Indicates that something is associated with a specific kind or category of duration (e.g., temporary, permanent, short-term, long-term).
-
C.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
D.
hasOfficialDuration
Indicates the formally defined length of time associated with an event, process, or entity.
-
E.
hasTrailDuration
Indicates that an entity (such as a trail or route) is associated with a specific amount of time required to traverse or complete it.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66065c17081908a0bb6b8a7f16558 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10:08 a.m.