Triple
T2226948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton, Dorset, England |
E48672
|
entity |
| Predicate | usedAsNameSourceFor |
P36337
|
FINISHED |
| Object | New England settlements |
—
|
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: New England settlements | Statement: [Milton, Dorset, England, usedAsNameSourceFor, New England settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNameSourceFor Context triple: [Milton, Dorset, England, usedAsNameSourceFor, New England settlements]
-
A.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
B.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
C.
hasGivenNameUsage
Indicates that an entity is associated with a particular way or context in which its given name is used.
-
D.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
E.
currentNameUsedFrom
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0411e388190b35e82ad6688bfe3 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.