Triple
T28210610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corbett, Scotland |
E711153
|
entity |
| Predicate | hasNotableNameType |
P100615
|
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: [Corbett, Scotland, hasNotableNameType, topographic surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNameType Context triple: [Corbett, Scotland, hasNotableNameType, topographic surname]
-
A.
hasNotableNamesakeType
chosen
Indicates that an entity has a notable namesake of a specified type (such as a person, place, or work) that shares its name.
-
B.
isNotableNameOf
Indicates that a name is widely recognized or distinguished as a significant identifier for the referenced entity.
-
C.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
D.
hasNotablePropertyNamedAfter
Indicates that an entity possesses a notable property or attribute that is named in honor of, or derived from, another entity.
-
E.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
Created at: April 27, 2026, 10:38 p.m.