Triple
T9777461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istari |
E237283
|
entity |
| Predicate | forbiddenAction |
P38719
|
FINISHED |
| Object | to dominate Elves and Men |
—
|
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: to dominate Elves and Men | Statement: [Istari, forbiddenAction, to dominate Elves and Men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forbiddenAction Context triple: [Istari, forbiddenAction, to dominate Elves and Men]
-
A.
refusedAction
Indicates that an entity deliberately declined or did not agree to perform a specific action requested, expected, or proposed by another entity.
-
B.
attemptedAction
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
C.
deniedAuthorityOf
Indicates that one entity refused to recognize, accept, or submit to the authority, power, or legitimacy of another entity.
-
D.
isProhibitedFor
chosen
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
E.
doesNotAllow
Indicates that one entity prevents, forbids, or does not permit another entity from performing a specific action or being in a certain state.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda133ef548190aaecdf49de9c5aa8 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:26 p.m.