Triple
T38359504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodman family |
E1046432
|
entity |
| Predicate | typeOfEponym |
—
|
GENERATED |
| Object | local landowning family |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEponym Context triple: [Rodman family, typeOfEponym, local landowning family]
-
A.
eponymLatinName
Indicates that one entity is the Latin name that is an eponym derived from or named after another entity.
-
B.
hasEponymCategory
Indicates that one entity serves as the namesake or eponym for the category or class represented by the other entity.
-
C.
eponymFor
Indicates that one entity gives its name to another entity, which is then named after it.
-
D.
hasEponymType
chosen
Indicates that something is associated with or classified by a particular type of eponym (a name derived from a person).
-
E.
eponymProfession
Indicates that a person’s profession is the source of an eponym, i.e., a word or name derived from that professional role.
- F. None of above.
Provenance (1 batch)
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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:31 p.m.