Triple
T36366983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prejmer fortified church |
E895651
|
entity |
| Predicate | builderEthnicGroup |
P150885
|
FINISHED |
| Object | Transylvanian Saxons |
—
|
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: Transylvanian Saxons | Statement: [Prejmer fortified church, builderEthnicGroup, Transylvanian Saxons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builderEthnicGroup Context triple: [Prejmer fortified church, builderEthnicGroup, Transylvanian Saxons]
-
A.
creatorEthnicGroup
Indicates that an entity was created by a person or group belonging to a specified ethnic group.
-
B.
ethnicGroupBase
Indicates that one entity serves as the primary or foundational ethnic group from which another entity is derived, associated, or defined.
-
C.
otherEthnicGroup
Indicates that one entity belongs to a different ethnic group than the other entity.
-
D.
ethnicGroupNamed
Indicates that an ethnic group bears or is identified by a particular name.
-
E.
ethnicOrCulturalGroup
chosen
Indicates that one entity belongs to, is associated with, or is characterized by a particular ethnic or cultural group represented by the other 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:10 p.m.