Triple
T27963551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cenchreae |
E704652
|
entity |
| Predicate | hasTitleInText |
P3254
|
FINISHED |
| Object | church in Cenchreae |
—
|
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: church in Cenchreae | Statement: [Cenchreae, hasTitleInText, church in Cenchreae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleInText Context triple: [Cenchreae, hasTitleInText, church in Cenchreae]
-
A.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
B.
hasTitleInName
Indicates that an entity’s name explicitly includes a specified title as part of it.
-
C.
containsTitle
chosen
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
D.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
E.
hasTitleFrom
Indicates that one entity holds or uses a title that originates from, or is conferred by, another entity.
- 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_69ef841061e48190b5570f9562f7434d |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 27, 2026, 7:33 p.m.