Triple
T29486749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nye Mountain |
E747944
|
entity |
| Predicate | approachCharacter |
P57748
|
FINISHED |
| Object | challenging |
—
|
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: challenging | Statement: [Nye Mountain, approachCharacter, challenging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachCharacter Context triple: [Nye Mountain, approachCharacter, challenging]
-
A.
followsCharacterTo
Indicates that one character moves after or in pursuit of another character to a particular location or destination.
-
B.
followsCharacterThrough
Indicates that one entity persistently tracks or accompanies a specific character along their path, perspective, or progression.
-
C.
pursuingCharacter
chosen
Indicates that one character is actively chasing, seeking, or attempting to catch or reach another character.
-
D.
trackCharacter
Indicates that one entity follows, monitors, or keeps a record of another entity’s actions, state, or progression over time.
-
E.
followsCharacter
Indicates that one character moves or acts after another character, maintaining a trailing or subsequent position or sequence relative to them.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 28, 2026, 4:09 p.m.