Triple
T38287377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesee Park |
E1022252
|
entity |
| Predicate | bisonHerdPurpose |
P190609
|
FINISHED |
| Object | public viewing |
—
|
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: public viewing | Statement: [Genesee Park, bisonHerdPurpose, public viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bisonHerdPurpose Context triple: [Genesee Park, bisonHerdPurpose, public viewing]
-
A.
pastoralPurpose
Indicates that something is intended or designated for pastoral use, care, or ministry within a religious or spiritual context.
-
B.
frozenZooPurpose
Indicates that the relationship or action concerns the purpose or intended use of a frozen zoo (a facility preserving genetic material of organisms).
-
C.
breedingGoal
Indicates that one entity is the intended objective or target outcome of a breeding process involving another entity.
-
D.
bears
Indicates that one entity carries, supports, or endures the weight, burden, or responsibility of another entity or condition.
-
E.
bearsConcept
Indicates that one entity carries, expresses, or embodies a particular concept in relation to another.
- 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_69f76df190f081908d5aa02c8a9286d0 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fccbd6b7688190b746803cf78d5704 |
completed | May 7, 2026, 5:28 p.m. |
Created at: May 3, 2026, 4:30 p.m.