Triple
T36556056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lossarnach |
E901700
|
entity |
| Predicate | sendsLeaderTo |
P185849
|
FINISHED |
| Object | the mustering at Minas Tirith |
—
|
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: the mustering at Minas Tirith | Statement: [Lossarnach, sendsLeaderTo, the mustering at Minas Tirith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sendsLeaderTo Context triple: [Lossarnach, sendsLeaderTo, the mustering at Minas Tirith]
-
A.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
-
B.
linkedToLeader
Indicates that an entity has a direct connection, association, or relationship with a leader.
-
C.
newLeader
Indicates that an entity has assumed a leadership role, typically replacing a previous leader or marking the start of a new leadership term.
-
D.
savesLeader
Indicates that one entity rescues, protects, or preserves the life, position, or well-being of a leader.
-
E.
laterLeader
Indicates that one entity serves as a leader or holds a leadership role at a later time than another specified leader.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.