Triple
T1850114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Maine |
E41374
|
entity |
| Predicate | naturalAttraction |
P7335
|
FINISHED |
| Object | mountain scenery |
—
|
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: mountain scenery | Statement: [Western Maine, naturalAttraction, mountain scenery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: naturalAttraction Context triple: [Western Maine, naturalAttraction, mountain scenery]
-
A.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
B.
followsNaturalFeature
Indicates that one entity’s position, path, or boundary runs alongside or is aligned with a natural geographic feature (such as a river, coastline, or ridgeline).
-
C.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
-
D.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
E.
touristAttractionIn
chosen
Indicates that a place functions as a tourist attraction located within a specified geographic area or 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.