Triple
T32955993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time Trax |
E843100
|
entity |
| Predicate | hasAIElement |
P48031
|
FINISHED |
| Object | holographic computer assistant Selma |
—
|
NE NERFINISHED |
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: holographic computer assistant Selma | Statement: [Time Trax, hasAIElement, holographic computer assistant Selma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAIElement Context triple: [Time Trax, hasAIElement, holographic computer assistant Selma]
-
A.
hasAI
chosen
Indicates that one entity possesses, incorporates, or is equipped with an artificial intelligence system.
-
B.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
C.
hasBruteElement
Indicates that an entity possesses or is associated with a raw, force-based, or brute-type elemental property.
-
D.
hasTechnicalElement
Indicates that something includes, involves, or is characterized by a technical component, feature, or aspect.
-
E.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d172304c819084a6f320ef4c847e |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:21 a.m.