Triple
T17159183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyer family (local ranchers) |
E416429
|
entity |
| Predicate | reasonForEponym |
P9593
|
FINISHED |
| Object | prominence as local ranchers |
—
|
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: prominence as local ranchers | Statement: [Dyer family (local ranchers), reasonForEponym, prominence as local ranchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEponym Context triple: [Dyer family (local ranchers), reasonForEponym, prominence as local ranchers]
-
A.
eponymFor
Indicates that one entity gives its name to another entity, which is then named after it.
-
B.
reasonForEpithet
chosen
Indicates the cause, motivation, or circumstance that explains why a particular epithet is applied to an entity.
-
C.
fieldOfEponym
Indicates the domain, discipline, or area of activity in which an eponymous name (e.g., a person or thing something is named after) is recognized or relevant.
-
D.
eponymKnownFor
Indicates that a person or entity is widely recognized or named as the source or inspiration for something else (such as a concept, place, or object).
-
E.
speciesEponym
Indicates that a species is named in honor of a particular person or entity.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f9103e3881908e76cea1c4880779 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.