Triple
T2406539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emneth |
E50287
|
entity |
| Predicate | hasChurchFeature |
P39232
|
FINISHED |
| Object | medieval tower |
—
|
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: medieval tower | Statement: [Emneth, hasChurchFeature, medieval tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChurchFeature Context triple: [Emneth, hasChurchFeature, medieval tower]
-
A.
hasChurch
Indicates that a place or entity possesses, contains, or is associated with a church.
-
B.
hasCongregation
Indicates that an entity is associated with or serves as the gathering place or organized group of worshippers for a religious community.
-
C.
hasMemberChurch
Indicates that a particular church is a constituent member of a larger religious organization, denomination, or church body.
-
D.
hasChurchmanship
Indicates that an entity adheres to or is associated with a particular style, tradition, or practice within a Christian church.
-
E.
hasCathedralChapter
Indicates that an ecclesiastical jurisdiction or church possesses or is served by a cathedral chapter as its governing or advisory body.
- F. None of above. chosen
Provenance (4 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_69a88b0339a88190a1207333cd271cc9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abceab9ce881909ae0a2f34515c11e |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5a530e8819094105aa92dfaf6b3 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abceaa42b88190a790355100fede3d |
completed | March 7, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:58 p.m.