Triple
T37100706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Mauch Chunk |
E918693
|
entity |
| Predicate | hasPresentNameOfTown |
P136607
|
FINISHED |
| Object | Jim Thorpe |
E267628
|
NE 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: Jim Thorpe | Statement: [East Mauch Chunk, hasPresentNameOfTown, Jim Thorpe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresentNameOfTown Context triple: [East Mauch Chunk, hasPresentNameOfTown, Jim Thorpe]
-
A.
hasNameInMunicipality
Indicates that an entity is known by a particular name within the context or jurisdiction of a specific municipality.
-
B.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
C.
hasMunicipalUnitName
chosen
Indicates that an entity is associated with the specific name of a municipal unit (such as a town, district, or local administrative division).
-
D.
isVillageNameOf
Indicates that a given name is the official or recognized name of a particular village.
-
E.
hasMunicipalSeatName
Indicates that an administrative unit’s municipal seat (its main town or city of government) has the specified name.
- F. None of above.
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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3efdd2e4a88190b83648ebb7a68b96 |
completed | June 26, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.