Triple
T38494389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagorlad |
E919647
|
entity |
| Predicate | aftermathFeature |
P191434
|
FINISHED |
| Object | Dead Marshes |
—
|
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: Dead Marshes | Statement: [Dagorlad, aftermathFeature, Dead Marshes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aftermathFeature Context triple: [Dagorlad, aftermathFeature, Dead Marshes]
-
A.
aftermathDescription
Indicates the description or characterization of events, conditions, or consequences that occur following a particular incident or action.
-
B.
aftermathOf
Indicates that one event, state, or condition occurs as a consequence or result following another event.
-
C.
aftermathDepictedIn
Indicates that the aftermath or consequences of an event or situation are depicted or represented in a given medium or work.
-
D.
aftermathActivity
Indicates the activity or state that occurs as a direct consequence of, or in response to, a preceding event or situation.
-
E.
aftermathHonor
Indicates that an entity is honored, commemorated, or given recognition as a consequence of a prior event or outcome.
- 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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: May 3, 2026, 4:31 p.m.