Triple
T22243506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantom Eye |
E549782
|
entity |
| Predicate | intendedEndurance |
P40755
|
FINISHED |
| Object | 4 days |
—
|
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: 4 days | Statement: [Phantom Eye, intendedEndurance, 4 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedEndurance Context triple: [Phantom Eye, intendedEndurance, 4 days]
-
A.
intendedDuration
chosen
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
B.
endurance
Indicates the capacity of an entity to sustain an activity, state, or condition over an extended period without failure or significant loss of performance.
-
C.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
D.
durabilityTarget
Indicates that one entity serves as the object or aspect whose durability, resilience, or resistance to wear is being evaluated, affected, or specified by another entity or process.
-
E.
durabilityModel
Indicates a relationship where an entity is associated with a specific model or method used to estimate or characterize its durability over time or under certain conditions.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1321655b0819091f1ddf06c67f3c2 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:38 p.m.