Triple
T158050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pauline Epistles |
E3220
|
entity |
| Predicate | addressesAudience |
P265
|
FINISHED |
| Object | early Christian communities |
—
|
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: early Christian communities | Statement: [Pauline Epistles, addressesAudience, early Christian communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesAudience Context triple: [Pauline Epistles, addressesAudience, early Christian communities]
-
A.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
B.
approximateAudienceSize
Indicates an estimated number of individuals or entities that are expected to be reached or affected in a given context.
-
C.
audienceSizeApproximate
Indicates an estimated or approximate number of people in the audience for an event or content.
-
D.
addresses
chosen
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
E.
scopeOfRecipients
Indicates the range or group of recipients to whom something (such as information, communication, or benefits) is directed or applicable.
- 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.