Triple
T7453442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eldritch Press |
E172060
|
entity |
| Predicate | makesAvailable |
P1395
|
FINISHED |
| Object | full-text editions |
—
|
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: full-text editions | Statement: [Eldritch Press, makesAvailable, full-text editions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: makesAvailable Context triple: [Eldritch Press, makesAvailable, full-text editions]
-
A.
availableAs
chosen
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
B.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of another entity.
-
C.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
D.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
E.
announcedAvailability
Indicates that an entity has publicly communicated that something will be obtainable or accessible, typically starting at a specified time or under certain conditions.
- 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_69c68a66554c8190add75c65942c0317 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f3ac5c2081908ab03f8bd4586f94 |
completed | March 27, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:14 p.m.