Triple
T23960371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanson |
E603908
|
entity |
| Predicate | isIncorporatedAs |
P19845
|
FINISHED |
| Object | town of Hanson |
—
|
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: town of Hanson | Statement: [Hanson, isIncorporatedAs, town of Hanson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIncorporatedAs Context triple: [Hanson, isIncorporatedAs, town of Hanson]
-
A.
incorporatedAs
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
-
B.
incorporatedStatus
Indicates whether an entity has been legally formed and registered as a corporation or similar incorporated organization.
-
C.
isIncorporatedPlace
chosen
Indicates that a location is a legally established, self-governing municipal entity (such as a city, town, or village) recognized as an incorporated place.
-
D.
incorporatedThrough
Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary entity.
-
E.
underlyingIncorporatedIn
Indicates that one entity serves as the foundational or base component that has been formally included or integrated into 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0da04cc8190a8d55512d4c7efdd |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:23 p.m.