Triple
T22320612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnacunnet |
E551772
|
entity |
| Predicate | nameUsedBefore |
P147725
|
FINISHED |
| Object | incorporation of Hampton, New Hampshire |
—
|
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: incorporation of Hampton, New Hampshire | Statement: [Winnacunnet, nameUsedBefore, incorporation of Hampton, New Hampshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameUsedBefore Context triple: [Winnacunnet, nameUsedBefore, incorporation of Hampton, New Hampshire]
-
A.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
B.
nameReusedFor
Indicates that an existing name has been used again for a different entity or instance, rather than introducing a completely new name.
-
C.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
D.
nameTakenAfter
Indicates that one entity received or adopted its name after, and in reference to, another entity.
-
E.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
- 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_69e11e4776588190abb21e5cea79973f |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15763bf0881908d859f85b4a6ce28 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e73004d9e88190bb862319a5aea06b |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:42 p.m.