Triple
T19574704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greg family (mill owners) |
E489821
|
entity |
| Predicate | businessPeak |
P3516
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Greg family (mill owners), businessPeak, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: businessPeak Context triple: [Greg family (mill owners), businessPeak, early 19th century]
-
A.
businessScale
Indicates the relative size or level of operations of a business, such as its scope, capacity, or market reach.
-
B.
commercialPeak
chosen
Indicates the time or period when something (such as a product, artist, or business) achieves its highest level of commercial success or popularity.
-
C.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
businessVenture
Indicates a relationship where entities jointly engage in, operate, or are involved with a commercial or entrepreneurial undertaking.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64023fe148190900c6887896c8ea0 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.