Triple
T8446437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incubus (in some traditions) |
E199687
|
entity |
| Predicate | wardedOffBy |
P83406
|
FINISHED |
| Object | prayer |
—
|
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: prayer | Statement: [Incubus (in some traditions), wardedOffBy, prayer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wardedOffBy Context triple: [Incubus (in some traditions), wardedOffBy, prayer]
-
A.
forfeitedBy
Indicates that something (such as a right, claim, or asset) is lost or given up as a consequence of the actions or failure of a particular entity.
-
B.
positionAwarded
Indicates that a specific position, role, or title has been formally granted to an entity (such as a person or organization).
-
C.
notAwardedFor
Indicates that a particular award, prize, or honor was explicitly not given in recognition of a specified work, achievement, or entity.
-
D.
rejectedAward
Indicates that an entity refused to accept or declined an award that was offered or granted to it.
-
E.
hasAwarded
Indicates that one entity has given or conferred an award to another entity.
- 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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe3152a3c819092efdeab718def7a |
completed | March 31, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69cbd0f5a3648190beb53a139a2d5482 |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe30c2d088190b4cb89adb4e88273 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:09 p.m.