Triple
T36547961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Foe of the World |
E901183
|
entity |
| Predicate | scopeOfEnmity |
P100775
|
FINISHED |
| Object | all the world |
—
|
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: all the world | Statement: [Black Foe of the World, scopeOfEnmity, all the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfEnmity Context triple: [Black Foe of the World, scopeOfEnmity, all the world]
-
A.
hostilityRange
chosen
Indicates the distance within which an entity will treat another as a hostile target and may initiate or respond with aggressive actions.
-
B.
feudedWith
Indicates a prolonged, often hostile conflict or rivalry between two entities.
-
C.
temporarilyEnemyOf
Indicates a relationship where two entities are in a state of enmity or opposition for a limited, non-permanent period of time.
-
D.
initiallyEnemyOf
Indicates that one entity starts out in a state of enmity or opposition toward another at the beginning of a specified time or situation.
-
E.
wasEnemyOf
Indicates that one entity regarded or interacted with another as an adversary or opponent, typically in a hostile or conflicting relationship.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.