Triple
T7989098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruder Klaus Field Chapel |
E185755
|
entity |
| Predicate | exteriorCharacter |
P80209
|
FINISHED |
| Object | simple geometric volume |
—
|
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: simple geometric volume | Statement: [Bruder Klaus Field Chapel, exteriorCharacter, simple geometric volume]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exteriorCharacter Context triple: [Bruder Klaus Field Chapel, exteriorCharacter, simple geometric volume]
-
A.
eraCharacter
Indicates that a character is associated with, or belongs to, a particular historical or fictional era.
-
B.
character1
Indicates that the subject is identified as the first or primary character in a narrative or context.
-
C.
character3
Indicates a tertiary or additional character role associated with an entity, typically the third distinct character linked within a given context or work.
-
D.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
-
E.
componentCharacter1
Indicates that one entity is the first (primary) character component or constituent part of another entity.
- 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_69ca829a2cfc819083d591d58ec04075 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c4e47308190918b67fb6eac9046 |
completed | March 31, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:16 p.m.