Triple
T37750365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fenced Land |
E940964
|
entity |
| Predicate | laterSackedBy |
P203230
|
FINISHED |
| Object | Sons of Fëanor |
—
|
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: Sons of Fëanor | Statement: [The Fenced Land, laterSackedBy, Sons of Fëanor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSackedBy Context triple: [The Fenced Land, laterSackedBy, Sons of Fëanor]
-
A.
wasSackedBy
Indicates that one entity was dismissed or fired from a position or role by another entity.
-
B.
sackedDuring
Indicates that one entity was dismissed or fired from a position during the time period or event represented by another entity.
-
C.
sackedBy
Indicates that one entity was dismissed or fired from a position or job by another entity.
-
D.
sackedIn
Indicates that one entity was dismissed or fired from a position or job in a particular location or context.
-
E.
sacked
Indicates that one entity has dismissed or removed another from a position, role, or employment, typically as an authoritative or punitive action.
- 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_69f76ee1f3a88190834e6c8af99bccc9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
| PDg | Predicate description generation | batch_6a013e22bf3881909c8d7dc301966aa5 |
completed | May 11, 2026, 2:25 a.m. |
Created at: May 3, 2026, 4:19 p.m.