Triple
T32206710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Rivendell |
E822690
|
entity |
| Predicate | holderAlliesWith |
P136406
|
FINISHED |
| Object | Gandalf |
—
|
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: Gandalf | Statement: [Lord of Rivendell, holderAlliesWith, Gandalf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderAlliesWith Context triple: [Lord of Rivendell, holderAlliesWith, Gandalf]
-
A.
hasPoliticalAlly
Indicates that one entity supports and cooperates with another in a political context, treating them as an ally in political activities or objectives.
-
B.
alliesOf
chosen
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
-
C.
oftenAlliedWith
Indicates that one entity is frequently or habitually allied or aligned in cooperation with another entity.
-
D.
alliedWithBasedOn
Indicates a relationship where two or more entities are allied with each other specifically due to, or grounded in, a particular basis, condition, or shared factor.
-
E.
alliesIncluded
Indicates that the specified set or group explicitly includes one or more allied entities as members.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 12:36 a.m.