Triple
T5755724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Silver Ghost |
E126960
|
entity |
| Predicate | testRunPurpose |
P36935
|
FINISHED |
| Object | demonstrate reliability |
—
|
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: demonstrate reliability | Statement: [Rolls-Royce Silver Ghost, testRunPurpose, demonstrate reliability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testRunPurpose Context triple: [Rolls-Royce Silver Ghost, testRunPurpose, demonstrate reliability]
-
A.
testRuns
Indicates that an entity executes or performs a test or series of tests on another entity or system.
-
B.
testSeriesPurpose
chosen
Indicates that a test series is conducted with the specific purpose or objective of achieving a particular outcome or goal.
-
C.
pilotRun
Indicates that an entity conducts or participates in a preliminary or trial implementation of a process, system, or project to test and evaluate it before full-scale deployment.
-
D.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
E.
testingMethod
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
- 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_69c00832aedc81909899801b141fa3b4 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02906848c8190bf7b0d62f57c27fa |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.