Triple
T3169711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Climb Ev'ry Mountain |
E66296
|
entity |
| Predicate | functionInPlot |
P32087
|
FINISHED |
| Object | motivational guidance for Maria |
—
|
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: motivational guidance for Maria | Statement: [Climb Ev'ry Mountain, functionInPlot, motivational guidance for Maria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInPlot Context triple: [Climb Ev'ry Mountain, functionInPlot, motivational guidance for Maria]
-
A.
hasFunctionInPlot
chosen
Indicates that an entity serves a particular role or purpose within the structure or progression of a plot.
-
B.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
C.
coordinateFunction
Indicates a functional relationship that maps or translates one set of coordinates to another within a defined space or system.
-
D.
functionInName
Indicates that the name of one entity includes or references the function or role of another entity.
-
E.
artisticFunction
Indicates that one entity serves a creative, expressive, or aesthetic role or purpose in relation to another 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_69ad8585d7988190af37365331093ccd |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada64917e08190bf0466d2c5e43790 |
completed | March 8, 2026, 4:39 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0076b4819094628f1ad10b8f68 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:06 p.m.