Triple
T29984818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle North Falls |
E761700
|
entity |
| Predicate | hasTrailBehindFalls |
P196421
|
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: [Middle North Falls, hasTrailBehindFalls, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailBehindFalls Context triple: [Middle North Falls, hasTrailBehindFalls, yes]
-
A.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
B.
trailsBehind
Indicates that one entity follows or moves after another, remaining at a distance behind it in space, time, or progress.
-
C.
hasTrailFeature
Indicates that a trail possesses or is characterized by a specific feature or attribute.
-
D.
hasNearbyFell
Indicates that one entity has a fell (a hill or high moorland area) located in close proximity to it.
-
E.
hasSideTrails
Indicates that a main path or route is accompanied by additional, smaller trails branching off from it.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
| PDg | Predicate description generation | batch_69fe349739cc8190a21c408208312e6c |
completed | May 8, 2026, 7:08 p.m. |
Created at: April 29, 2026, 6:36 p.m.