Triple
T3087815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livermore Falls, Maine |
E64414
|
entity |
| Predicate | isPopulatedPlace |
P45808
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Livermore Falls, Maine, isPopulatedPlace, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopulatedPlace Context triple: [Livermore Falls, Maine, isPopulatedPlace, true]
-
A.
isPopulatedPlaceIn
Indicates that a populated place (such as a city, town, or village) is located within a specified larger geographic or administrative area.
-
B.
typeOfToponym
Indicates the specific category or kind of place name (toponym) that applies to a given geographic entity.
-
C.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
D.
isIncorporatedPlace
Indicates that a location is a legally established, self-governing municipal entity (such as a city, town, or village) recognized as an incorporated place.
-
E.
isMajorAdministrativeCentre
Indicates that a location functions as the primary hub for governmental and administrative activities within a larger region or jurisdiction.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada209fd24819088d887de0a4158f4 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:03 p.m.