Triple
T8430699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faramir |
E199106
|
entity |
| Predicate | ringReaction |
P83312
|
FINISHED |
| Object | Refuses to take the One Ring from Frodo |
—
|
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: Refuses to take the One Ring from Frodo | Statement: [Faramir, ringReaction, Refuses to take the One Ring from Frodo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringReaction Context triple: [Faramir, ringReaction, Refuses to take the One Ring from Frodo]
-
A.
sideReaction
Indicates that one reaction occurs as an unintended or secondary process alongside a primary reaction.
-
B.
reactionType
Indicates the specific kind or category of reaction that occurs between entities or in response to an event or stimulus.
-
C.
fusionReactionExample
Indicates that one entity serves as an example or instance of a specific fusion reaction involving the other entity.
-
D.
fusionReactionType
Indicates the specific kind or category of nuclear fusion process that relates two or more participating entities.
-
E.
relatedReaction
Indicates that one reaction is connected or associated with another reaction in some relevant way.
- 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:07 p.m.