Triple
T11616205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniacke |
E275514
|
entity |
| Predicate | hasEponymousRelationTo |
P56375
|
FINISHED |
| Object | place names |
—
|
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: place names | Statement: [Uniacke, hasEponymousRelationTo, place names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEponymousRelationTo Context triple: [Uniacke, hasEponymousRelationTo, place names]
-
A.
hasEponymConnectionTo
chosen
Indicates that one entity is named after, derived from, or otherwise linguistically or honorifically connected to another entity as its eponym.
-
B.
hasEponymFamilyRelation
Indicates that one entity is named after another entity to which it is related by family or kinship.
-
C.
hasEponymSpouse
Indicates that one entity has a spouse after whom it is named or whose name it bears.
-
D.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
E.
isRelatedName
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a04675e08190837a3717242fd0f9 |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.