Triple
T10649079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brampton Assembly |
E250913
|
entity |
| Predicate | assemblyLineType |
P17333
|
FINISHED |
| Object | vehicle assembly |
—
|
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: vehicle assembly | Statement: [Brampton Assembly, assemblyLineType, vehicle assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblyLineType Context triple: [Brampton Assembly, assemblyLineType, vehicle assembly]
-
A.
hasAssemblyLineFor
chosen
Indicates that one entity operates or contains an assembly line specifically used to produce, process, or assemble another entity.
-
B.
servedLineType
Indicates the type or category of service line associated with or provided in a given context.
-
C.
servesLineType
Indicates that a service or entity operates or supports a specific type or category of line (e.g., transport, communication, or utility line).
-
D.
instructionSetType
Indicates the type or category of an instruction set associated with a processor or computing architecture.
-
E.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfe3ea08819094a945ebb7fc4d3a |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.