Triple
T11616188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniacke |
E275514
|
entity |
| Predicate | hasNotableNamesakeType |
P100615
|
FINISHED |
| Object | settlement |
—
|
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: settlement | Statement: [Uniacke, hasNotableNamesakeType, settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNamesakeType Context triple: [Uniacke, hasNotableNamesakeType, settlement]
-
A.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
-
B.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
C.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
D.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
E.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
- 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_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. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:38 p.m.