Triple
T158037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauline Epistles |
E3220
|
entity |
| Predicate | subcollection |
P1925
|
FINISHED |
| Object | undisputed Pauline letters |
—
|
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: undisputed Pauline letters | Statement: [Pauline Epistles, subcollection, undisputed Pauline letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subcollection Context triple: [Pauline Epistles, subcollection, undisputed Pauline letters]
-
A.
partOfCollection
chosen
Indicates that an entity belongs to, or is included within, a larger collection or set.
-
B.
subfamily
Indicates that one taxonomic group is a subfamily within a larger family, representing an intermediate rank in biological classification.
-
C.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
D.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
E.
subclassOf
Indicates that one class is a more specific type of another class, inheriting its characteristics as a subset of it.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.