Triple
T3618379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galt |
E76659
|
entity |
| Predicate | isIncorporatedCity |
P19845
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Galt, isIncorporatedCity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIncorporatedCity Context triple: [Galt, isIncorporatedCity, yes]
-
A.
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.
-
B.
incorporatedAsCity
Indicates that an entity was formally established and legally recognized as a city.
-
C.
isMunicipalCorporationOf
Indicates that an entity functions as the municipal governing body responsible for administering and managing the affairs of a specified city or urban area.
-
D.
isSubProvincialCity
Indicates that a city holds a sub-provincial administrative status, ranking below a province but above ordinary prefecture-level cities in the governmental hierarchy.
-
E.
isInCity
Indicates that one entity is located within the geographical boundaries of a specified city.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2b72b3481909f4a09000d1815d9 |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.