Triple
T26465373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signature Limited |
E665747
|
entity |
| Predicate | offeredOnModelType |
P176698
|
FINISHED |
| Object | full-size luxury sedan |
—
|
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: full-size luxury sedan | Statement: [Signature Limited, offeredOnModelType, full-size luxury sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredOnModelType Context triple: [Signature Limited, offeredOnModelType, full-size luxury sedan]
-
A.
offeredEngineType
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
B.
offeredOnGeneration
Indicates that something is proposed or made available at the moment it is created or generated.
-
C.
isOfferedBy
Indicates that a service, product, or opportunity is provided or made available by a particular entity.
-
D.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
-
E.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
- F. None of above. chosen
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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 27, 2026, 12:15 a.m.