Triple
T16295685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TriStar K1 |
E395639
|
entity |
| Predicate | serviceEntryWithRAF |
P21857
|
FINISHED |
| Object | 1980s |
—
|
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: 1980s | Statement: [TriStar K1, serviceEntryWithRAF, 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryWithRAF Context triple: [TriStar K1, serviceEntryWithRAF, 1980s]
-
A.
serviceEntryWith
Indicates that one entity is associated with or accompanied by a particular service entry in a joint or linked context.
-
B.
serviceEntryInROC
Indicates that a service entry is recorded or included in a Register of Companies (ROC) or similar official registry.
-
C.
serviceEntryContext
Indicates the contextual circumstances or environment in which a particular service entry is created, recorded, or applied.
-
D.
serviceEntryStatus
Indicates the current state or condition of a service entry within a process or system (e.g., whether it is active, pending, completed, or otherwise classified).
-
E.
enteredRAFService
chosen
Indicates that an entity began service in the Royal Air Force (RAF).
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e25e2d08108190bab1b3325923af1d |
completed | April 17, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69e219fa5508819097e9d383348bf174 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.