Triple
T23660749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond, Utah |
E584436
|
entity |
| Predicate | BlackAndWhiteDaysSpeciesFocus |
P152900
|
FINISHED |
| Object | Holstein cattle |
—
|
NE NERFINISHED |
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: Holstein cattle | Statement: [Richmond, Utah, BlackAndWhiteDaysSpeciesFocus, Holstein cattle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BlackAndWhiteDaysSpeciesFocus Context triple: [Richmond, Utah, BlackAndWhiteDaysSpeciesFocus, Holstein cattle]
-
A.
someSpeciesAre
Indicates that at least one member of a specified group or category belongs to, or can be classified as, a particular species.
-
B.
typicalWildlifeObserved
Indicates that certain wildlife species are commonly or characteristically observed in a given area or context.
-
C.
hasBirdSpecies
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
-
D.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
E.
conservationFocusSpecies
Indicates that a conservation effort, program, or context is specifically directed toward or centered on a particular species.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35f03448190834991c2a65ef0e4 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:50 p.m.