Triple
T8751564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berea |
E207970
|
entity |
| Predicate | hasChristianCommunitySince |
P11795
|
FINISHED |
| Object | 1st century AD |
—
|
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: 1st century AD | Statement: [Berea, hasChristianCommunitySince, 1st century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChristianCommunitySince Context triple: [Berea, hasChristianCommunitySince, 1st century AD]
-
A.
hasChristianCommunity
chosen
Indicates that a place or entity possesses or hosts an established Christian community.
-
B.
congregationFounded
Indicates that a particular congregation was established or created at a certain time or by a certain founding event or agent.
-
C.
hasContinuousReligiousFunctionSince
Indicates that a religious function or use has been ongoing without interruption from a specified starting time up to the present or another reference time.
-
D.
isEstablishedChurchIn
Indicates that a church is officially recognized and established as the state or national church within a specified jurisdiction or territory.
-
E.
establishedAsCongregationBy
Indicates that an entity was formally created or organized as a congregation by another specified agent or authority.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da774f4819099e5bfd12973d946 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.