Triple
T36313941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hart-Parr Company |
E894137
|
entity |
| Predicate | primaryUseOfProducts |
P131315
|
FINISHED |
| Object | mechanization of farm work |
—
|
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: mechanization of farm work | Statement: [Hart-Parr Company, primaryUseOfProducts, mechanization of farm work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseOfProducts Context triple: [Hart-Parr Company, primaryUseOfProducts, mechanization of farm work]
-
A.
primaryUseOf
chosen
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
B.
primaryHumanUse
Indicates the main way humans typically use, interact with, or benefit from the referenced entity.
-
C.
primaryProduct
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
D.
formerPrimaryUse
Indicates that something was previously used as the main or principal function or purpose of an entity, but is no longer its current primary use.
-
E.
productionPurpose
Indicates that something is created, manufactured, or produced specifically for a particular use, goal, or intended function.
- 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_69f76e4d1a788190a6ab6ccca28547a7 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.