Triple
T37142341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falas |
E920147
|
entity |
| Predicate | sackedDuring |
P187188
|
FINISHED |
| Object | Invasion of Beleriand by Morgoth |
—
|
NE NERFINISHED |
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: Invasion of Beleriand by Morgoth | Statement: [Falas, sackedDuring, Invasion of Beleriand by Morgoth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sackedDuring Context triple: [Falas, sackedDuring, Invasion of Beleriand by Morgoth]
-
A.
sackedIn
Indicates that one entity was dismissed or fired from a position or job in a particular location or context.
-
B.
sackedBy
Indicates that one entity was dismissed or fired from a position or job by another entity.
-
C.
sackedInYear
Indicates that an entity (such as a person in a role) was dismissed or fired from their position in a specified year.
-
D.
sacked
Indicates that one entity has dismissed or removed another from a position, role, or employment, typically as an authoritative or punitive action.
-
E.
wasSackedBy
Indicates that one entity was dismissed or fired from a position or role by another entity.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.