Triple
T8751559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berea |
E207970
|
entity |
| Predicate | hasReputationAmongChristians |
P61188
|
FINISHED |
| Object | model of scriptural diligence |
—
|
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: model of scriptural diligence | Statement: [Berea, hasReputationAmongChristians, model of scriptural diligence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReputationAmongChristians Context triple: [Berea, hasReputationAmongChristians, model of scriptural diligence]
-
A.
pietyReputation
Indicates the degree to which an entity is regarded as devout, virtuous, or religiously upright based on its perceived behavior or character.
-
B.
hasReputationAmong
chosen
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
C.
hasNotableReputation
Indicates that an entity is widely recognized or distinguished for a particular quality, achievement, or characteristic.
-
D.
hasChristianCommunity
Indicates that a place or entity possesses or hosts an established Christian community.
-
E.
hasQuirkyReputation
Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
- 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.