Triple
T6954006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Archer |
E161194
|
entity |
| Predicate | warpProgram |
P74261
|
FINISHED |
| Object | Warp 5 program |
—
|
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: Warp 5 program | Statement: [Jonathan Archer, warpProgram, Warp 5 program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warpProgram Context triple: [Jonathan Archer, warpProgram, Warp 5 program]
-
A.
componentProgram
Indicates that one entity is a component or module that forms part of a larger program or software system represented by the other entity.
-
B.
madeProgram
Indicates that one entity created, developed, or authored a program (such as software or a coded application).
-
C.
producedProgram
Indicates that one entity created or produced a specific program (such as a TV show, software, or other structured content).
-
D.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
E.
reconstructionProgram
Indicates a program or initiative designed to rebuild, restore, or structurally improve something that has been damaged, degraded, or is otherwise in need of renewal.
- 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_69c68852a9a0819097797e31d492e273 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dacca12481908942ba793a104cc3 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bf0a7c8190b5ed4aca22ba9b97 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dacb524c81909aade2282a4c0c01 |
completed | March 27, 2026, 7:30 p.m. |
Created at: March 27, 2026, 2:29 p.m.