Triple
T33924559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Type 200 |
E869711
|
entity |
| Predicate | relatedEngineManufacturer |
P86295
|
FINISHED |
| Object | Rolls-Royce Limited |
E25570
|
NE 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: Rolls-Royce Limited | Statement: [Bristol Type 200, relatedEngineManufacturer, Rolls-Royce Limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedEngineManufacturer Context triple: [Bristol Type 200, relatedEngineManufacturer, Rolls-Royce Limited]
-
A.
alsoManufacturedBy
Indicates that an item or product is produced by an additional manufacturer beyond the primary or previously mentioned one.
-
B.
vehicleBrandAssociated
Indicates that there is an association or linkage between a vehicle and a particular brand.
-
C.
carManufacturer
Indicates that one entity is the company that produces or manufactures the car represented by the other entity.
-
D.
droveManufacturer
Indicates that a person or agent operated or used a vehicle produced by a specific manufacturer.
-
E.
engineBrand
chosen
Indicates that one entity is the brand or manufacturer of the engine used by another entity.
- F. None of above.
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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a368253d3f081909ba6e5e21837c1b7 |
completed | June 20, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.