Triple
T11547885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolvar Fordragon |
E273815
|
entity |
| Predicate | reasonForTakingHelm |
P100077
|
FINISHED |
| Object | to contain the Scourge |
—
|
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: to contain the Scourge | Statement: [Bolvar Fordragon, reasonForTakingHelm, to contain the Scourge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForTakingHelm Context triple: [Bolvar Fordragon, reasonForTakingHelm, to contain the Scourge]
-
A.
reasonForScuttling
Indicates the specific cause or motivation that led to a vessel being deliberately scuttled.
-
B.
reasonForKnighthood
Indicates the specific cause, achievement, or merit for which an individual was granted knighthood.
-
C.
reasonForPledge
Indicates the motivation or justification behind making a particular pledge or commitment.
-
D.
reasonForEnlistment
Indicates the motivation, cause, or circumstances that led an individual to join a military or similar organized service.
-
E.
reasonForRaid
Indicates the underlying cause, motive, or justification for which a raid was initiated or carried out.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822f00a088190ac6b48e45e743899 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:37 p.m.