Triple
T25168004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jim Preston |
E630234
|
entity |
| Predicate | repairs |
P157982
|
FINISHED |
| Object | starship Avalon systems |
—
|
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: starship Avalon systems | Statement: [Jim Preston, repairs, starship Avalon systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repairs Context triple: [Jim Preston, repairs, starship Avalon systems]
-
A.
repairsCompleted
Indicates that a previously initiated repair action or process has been fully carried out and successfully finished.
-
B.
spares
Indicates that one entity chooses not to harm, punish, or destroy another entity when it has the power or opportunity to do so.
-
C.
repairedIn
Indicates that an item or object underwent repair within a specified location or during a particular time period.
-
D.
requiredFollowUpRepairsBy
Indicates that one entity necessitates subsequent repair work to be performed by another specific entity.
-
E.
maintenanceType
Indicates the specific category or kind of maintenance activity associated with an entity or relationship.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46d43e6d08190bbd8643ea058ceea |
completed | May 1, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 21, 2026, 12:18 p.m.