Triple
T22081590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jane of Lantern Hill |
E545661
|
entity |
| Predicate | hasEndingType |
P84433
|
FINISHED |
| Object | optimistic |
—
|
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: optimistic | Statement: [Jane of Lantern Hill, hasEndingType, optimistic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndingType Context triple: [Jane of Lantern Hill, hasEndingType, optimistic]
-
A.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
-
B.
hasTypeOfEnding
chosen
Indicates that one entity possesses or exhibits a particular kind or category of ending associated with another entity.
-
C.
hasConditionalEnding
Indicates that one entity concludes or terminates only if a specified condition involving another entity is met.
-
D.
hasEnd
Indicates that one entity serves as the terminal point, boundary, or conclusion of another entity or process.
-
E.
hasEndingTone
Indicates that something concludes with a particular tone, mood, or intonational quality.
- 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_69e11e3523488190badd54b5d580c00d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128b6338481908e6bb0187cdd42af |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:28 p.m.