Triple
T27782603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statler Motors |
E699372
|
entity |
| Predicate | hasFictionalServiceType |
P61295
|
FINISHED |
| Object | car sales |
—
|
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: car sales | Statement: [Statler Motors, hasFictionalServiceType, car sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalServiceType Context triple: [Statler Motors, hasFictionalServiceType, car sales]
-
A.
hasServiceType
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
fictionalService
chosen
Indicates that one entity provides or is associated with an imagined or non-real service in relation to another entity.
-
D.
hasLimitedServiceType
Indicates that an entity is associated with a service that is restricted in scope, availability, or functionality compared to full or standard service types.
-
E.
hasCommercialServices
Indicates that one entity provides or offers commercial services to another entity or within a specified context.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 5:11 p.m.