Triple
T25368192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lonach Games field |
E632859
|
entity |
| Predicate | traditionalUseSince |
P169516
|
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: [Lonach Games field, traditionalUseSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalUseSince Context triple: [Lonach Games field, traditionalUseSince, 19th century]
-
A.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
B.
traditionalUseDomain
Indicates that something is traditionally used or applied within a particular domain, field, or area of practice.
-
C.
traditionalUseRegion
Indicates the geographic region where something has been traditionally used or practiced.
-
D.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
E.
traditionalTerritoryUse
Indicates that an entity uses or occupies a territory in ways that follow long-established, customary, or ancestral practices.
- F. None of above. chosen
Provenance (4 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 21, 2026, 1:38 p.m.