Triple
T37184009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagor-nuin-Giliath |
E921273
|
entity |
| Predicate | takesPlaceAfterEvent |
P6702
|
FINISHED |
| Object | Dagor Bragollach |
—
|
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: Dagor Bragollach | Statement: [Dagor-nuin-Giliath, takesPlaceAfterEvent, Dagor Bragollach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesPlaceAfterEvent Context triple: [Dagor-nuin-Giliath, takesPlaceAfterEvent, Dagor Bragollach]
-
A.
tookPlaceAfter
chosen
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
B.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
-
C.
arisesAfter
Indicates that one event, state, or condition comes into existence or begins only after another specified event, state, or condition has occurred.
-
D.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
E.
actsBefore
Indicates that one entity performs an action or occurs in time prior to another entity or action.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.