Triple
T35753771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Cars Ltd |
E1033384
|
entity |
| Predicate | usedCoachworkFrom |
P4673
|
FINISHED |
| Object | Swallow Coachbuilding |
—
|
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: Swallow Coachbuilding | Statement: [SS Cars Ltd, usedCoachworkFrom, Swallow Coachbuilding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCoachworkFrom Context triple: [SS Cars Ltd, usedCoachworkFrom, Swallow Coachbuilding]
-
A.
usesCoachType
Indicates that an entity employs or operates a specific type or category of coach (e.g., vehicle or carriage) in its service or context.
-
B.
coachedFrom
Indicates that one entity served as a coach or trainer for another entity during a specified period or context.
-
C.
basedInAsCoach
Indicates that a person holds a coaching position for an organization or team that is located in a specified place.
-
D.
coachedAlongside
Indicates that two or more individuals served as coaches at the same time, typically for the same team, organization, or event.
-
E.
usedEquipmentFrom
chosen
Indicates that one entity has utilized or operated equipment that originated from or was provided by 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.