Triple
T30404515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabbia |
E773443
|
entity |
| Predicate | availableInModel |
P99156
|
FINISHED |
| Object | Lamborghini Urus |
—
|
NE NERFINISHED |
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: Lamborghini Urus | Statement: [Sabbia, availableInModel, Lamborghini Urus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableInModel Context triple: [Sabbia, availableInModel, Lamborghini Urus]
-
A.
availableInMode
Indicates that something can be used, accessed, or functions within a specified mode or operational setting.
-
B.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
C.
usedInDeviceModel
chosen
Indicates that something (such as a component, material, or technology) is utilized within or incorporated into a particular device model.
-
D.
mayBeAvailableIn
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
E.
possibleModel
Indicates that one entity can serve as a potential or candidate model or template for another entity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861c95e88190a5f3a4a6c952692a |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:03 p.m.