Triple
T34099156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recreation Park (Columbus) |
E874515
|
entity |
| Predicate | usedInYearsApprox |
P92184
|
FINISHED |
| Object | 1890s |
—
|
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: 1890s | Statement: [Recreation Park (Columbus), usedInYearsApprox, 1890s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInYearsApprox Context triple: [Recreation Park (Columbus), usedInYearsApprox, 1890s]
-
A.
yearOfUse
Indicates the specific year during which something was in use or actively utilized.
-
B.
appliesInYears
chosen
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
C.
usedByYears
Indicates the span of years during which something (such as a method, standard, or item) was in use by a particular entity.
-
D.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
E.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 1, 2026, 1:53 a.m.