Triple
T201642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Merlin |
E4518
|
entity |
| Predicate | firstRunDate |
P3273
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Rolls-Royce Merlin, firstRunDate, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRunDate Context triple: [Rolls-Royce Merlin, firstRunDate, 1933]
-
A.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
firstSessionStart
Indicates the point in time when an entity’s very first session or interaction begins.
-
C.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
D.
firstDeployed
chosen
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
E.
firstRaisedAt
Indicates the initial time or context at which an issue, topic, or matter was first brought up or introduced.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c2ead8481909996042efcae5e9d |
completed | Feb. 28, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69a25b4a0d448190a6fa6aeb30dc7e13 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.