Triple
T34586394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Purchase African M.E. Church |
E888054
|
entity |
| Predicate | visitedWithCharacter |
P142312
|
FINISHED |
| Object | Calpurnia |
—
|
NE NERFINISHED |
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: Calpurnia | Statement: [First Purchase African M.E. Church, visitedWithCharacter, Calpurnia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedWithCharacter Context triple: [First Purchase African M.E. Church, visitedWithCharacter, Calpurnia]
-
A.
visitedByCharacter
Indicates that a location or place is visited or physically gone to by a specific character.
-
B.
visitedWith
chosen
Indicates that one entity visited a place or another entity together with a companion entity during the same occasion.
-
C.
visitedBy
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
D.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
-
E.
visitedDuring
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f731cc6d1881908f80386ef4d70a09 |
completed | May 3, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69f7317779e08190bf85777578221a6b |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 2:03 a.m.