Triple
T35624704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keuka Outlet |
E1029416
|
entity |
| Predicate | historicalEraOfIndustrialUse |
P149688
|
FINISHED |
| Object | 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: 19th century | Statement: [Keuka Outlet, historicalEraOfIndustrialUse, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEraOfIndustrialUse Context triple: [Keuka Outlet, historicalEraOfIndustrialUse, 19th century]
-
A.
historicalPeriodOfIndustrialUse
chosen
Indicates the historical time span during which an entity was used for industrial purposes.
-
B.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
C.
historicalPeriodOfGreatestUse
Indicates the time period during which something was used most intensively or prevalently.
-
D.
historicalPeakIndustrialPeriod
Indicates the time period during which an entity reached its highest level of industrial activity or development.
-
E.
historicalPeriodOfNotableUse
Indicates the historical time period during which the entity was notably or most prominently used.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:05 p.m.