Triple
T6413917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adonijah |
E127774
|
entity |
| Predicate | soughtAsylumBy |
P70518
|
FINISHED |
| Object | taking hold of the horns of the altar |
—
|
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: taking hold of the horns of the altar | Statement: [Adonijah, soughtAsylumBy, taking hold of the horns of the altar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soughtAsylumBy Context triple: [Adonijah, soughtAsylumBy, taking hold of the horns of the altar]
-
A.
soughtAsylumAt
Indicates that an individual or group applied for protection or refuge at a particular country, institution, or authority.
-
B.
attemptedToSeekAsylumIn
Indicates that an entity tried, but may not have succeeded, to obtain asylum in a particular place or country.
-
C.
countryOfAsylum
Indicates that one entity serves as the country providing asylum or refuge to another entity.
-
D.
receivedAsylumFrom
Indicates that one entity was granted asylum or refuge by another entity, typically a state or institution.
-
E.
yearOfAsylum
Indicates the specific year in which an entity was granted or obtained asylum.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e5187c8190a6be1b934e0f1b3a |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:42 p.m.