Triple
T37340036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milwaukee-Eight 117 |
E927007
|
entity |
| Predicate | primaryDrive |
P135813
|
FINISHED |
| Object | chain-driven primary |
—
|
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: chain-driven primary | Statement: [Milwaukee-Eight 117, primaryDrive, chain-driven primary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDrive Context triple: [Milwaukee-Eight 117, primaryDrive, chain-driven primary]
-
A.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system or context.
-
B.
primaryStorageLocation
Indicates the main or default place where an item, resource, or data is stored.
-
C.
mechanicalDrive
chosen
Indicates a relationship where one entity transmits mechanical power or motion to another, typically via components like gears, belts, or shafts.
-
D.
primaryCpu
Indicates that one CPU is designated as the main or primary processing unit in relation to another component or system.
-
E.
primaryFile
Indicates that one file in a set is designated as the main or most important file associated with a given entity or 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_69f76eb4e8a881908bd40da28f36fc7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.