Triple
T25986885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hologram Janeway |
E646225
|
entity |
| Predicate | canProjectAs |
P159639
|
FINISHED |
| Object | interactive holographic avatar |
—
|
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: interactive holographic avatar | Statement: [Hologram Janeway, canProjectAs, interactive holographic avatar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canProjectAs Context triple: [Hologram Janeway, canProjectAs, interactive holographic avatar]
-
A.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
B.
authorizesProject
Indicates that one entity grants official permission or approval for another entity to initiate or carry out a project.
-
C.
authorizedProject
Indicates that a project has been formally approved or granted permission by the relevant authority to proceed or be used.
-
D.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
-
E.
byProject
Indicates that something is organized, grouped, or associated according to a specific project.
- F. None of above. chosen
Provenance (4 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605446ca48190907baef523f13ccf |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 22, 2026, 8:55 a.m.