Triple
T19505676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "The woods are lovely, dark and deep," |
E488014
|
entity |
| Predicate | precedesLineInPoem |
P136170
|
FINISHED |
| Object | "But I have promises to keep," |
—
|
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: "But I have promises to keep," | Statement: ["The woods are lovely, dark and deep,", precedesLineInPoem, "But I have promises to keep,"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesLineInPoem Context triple: ["The woods are lovely, dark and deep,", precedesLineInPoem, "But I have promises to keep,"]
-
A.
hasFeatureInPoem
Indicates that a poem includes or is characterized by a particular feature, element, or attribute.
-
B.
precedesSong
Indicates that one song comes before another song in a defined sequence, such as an album tracklist or playlist order.
-
C.
containsPoem
Indicates that one entity includes or holds a poem as part of its contents.
-
D.
hasRhymeLine
Indicates that one line of text rhymes with another line.
-
E.
precedesLetter
Indicates that one letter comes immediately before another letter in a specified ordering, such as the alphabet or a given sequence.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e635113fdc819098ea0f738d01925c |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004d3a708190a1c13c8f644f3926 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:40 p.m.