Triple
T1243366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arlington Assembly |
E26707
|
entity |
| Predicate | assemblyType |
P17334
|
FINISHED |
| Object | vehicle final 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 final assembly | Statement: [Arlington Assembly, assemblyType, vehicle final assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assemblyType Context triple: [Arlington Assembly, assemblyType, vehicle final assembly]
-
A.
hasAssemblyType
chosen
Indicates that an entity is associated with or classified by a specific type or method of assembly.
-
B.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
C.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
D.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
E.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf61fadc8190b7b9e23eaa15a61d |
completed | March 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.