Triple
T34957870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lifesigns |
E1008166
|
entity |
| Predicate | featuresDoctorAsHologram |
—
|
GENERATED |
| Object | yes |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDoctorAsHologram Context triple: [Lifesigns, featuresDoctorAsHologram, yes]
-
A.
hasEmergencyHologram
Indicates that an entity possesses or is equipped with an emergency hologram system available for use in critical or urgent situations.
-
B.
featuredDoctor
Indicates that a particular doctor is highlighted or promoted as a primary or notable medical professional in a given context.
-
C.
hasDoctorActor
Indicates that a doctor participates as an acting agent in the specified event or relationship.
-
D.
hasHolographicBodyCreatedBy
Indicates that an entity possesses a holographic body that was created by another specified entity.
-
E.
hasDoctorCharacter
chosen
Indicates that an entity includes or features a character whose role or profession is that of a doctor.
- F. None of above.
Provenance (1 batch)
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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.