Triple
T37142994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green-elves of Ossiriand |
E920165
|
entity |
| Predicate | afterEventBehavior |
P178649
|
FINISHED |
| Object | avoided large-scale battles |
—
|
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: avoided large-scale battles | Statement: [Green-elves of Ossiriand, afterEventBehavior, avoided large-scale battles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEventBehavior Context triple: [Green-elves of Ossiriand, afterEventBehavior, avoided large-scale battles]
-
A.
afterEventCommander
Indicates that one entity serves as the commander or leader responsible for an event that occurs after another specified event.
-
B.
changesAfterEvents
chosen
Indicates that one entity undergoes a change as a consequence of, or following, the occurrence of specified events.
-
C.
setAfterEventsOf
Indicates that one event or state is positioned or scheduled to occur after the completion of one or more specified preceding events.
-
D.
settingAfterEvent
Indicates that a particular setting or state occurs subsequent to, and as a result of or in temporal sequence with, a specified event.
-
E.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.