Triple
T11047218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Grey Havens |
E261163
|
entity |
| Predicate | survivedUntil |
P90053
|
FINISHED |
| Object | end of the Third Age |
—
|
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: end of the Third Age | Statement: [The Grey Havens, survivedUntil, end of the Third Age]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: survivedUntil Context triple: [The Grey Havens, survivedUntil, end of the Third Age]
-
A.
survivesFor
chosen
Indicates that one entity continues to exist, endure, or remain functional for a specified duration or period.
-
B.
survivesWith
Indicates that one entity continues to live, endure, or remain viable in the presence, context, or company of another entity.
-
C.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
-
D.
survivorTerm
Indicates that one entity is designated as the surviving or remaining party in relation to another entity, often after a loss, termination, or adverse event.
-
E.
survivedEvent
Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798307da481908996557a73c9b49a |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.