Triple
T24449817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillman |
E616501
|
entity |
| Predicate | isOccupationalOrTopographic |
P94821
|
FINISHED |
| Object | topographic surname |
—
|
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: topographic surname | Statement: [Hillman, isOccupationalOrTopographic, topographic surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOccupationalOrTopographic Context triple: [Hillman, isOccupationalOrTopographic, topographic surname]
-
A.
isOccupationalOrToponymic
chosen
Indicates that a name or term is derived either from an occupation (job or role) or from a place (toponymic origin).
-
B.
isToponymic
Indicates that something is related to or derived from a place name (a toponym).
-
C.
hasTopographicalRole
Indicates that an entity serves a specific functional or positional role within a topographical or spatial context.
-
D.
hasToponymicUse
Indicates that a term or name is used as a toponym, i.e., as a place name or geographic designation.
-
E.
hasTypeOfToponym
Indicates that one entity is classified as a specific type or category of toponym (place name) in relation to another 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298562c6c8190a7374508f7237be2 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.