Triple
T35101766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberhaus |
E1013037
|
entity |
| Predicate | historicalEquivalentOf |
P152886
|
FINISHED |
| Object | Erste Kammer |
—
|
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: Erste Kammer | Statement: [Oberhaus, historicalEquivalentOf, Erste Kammer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalEquivalentOf Context triple: [Oberhaus, historicalEquivalentOf, Erste Kammer]
-
A.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
B.
historicalTermFor
chosen
Indicates that one term was historically used to refer to, describe, or name the other entity in an earlier time or context.
-
C.
historicallyRecognizedAs
Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
-
D.
historicalPeg
Indicates a relationship where one entity’s value, status, or definition was formerly fixed or tied to another entity in the past.
-
E.
historicalConcept
Indicates that something represents, embodies, or is recognized as a concept, idea, or notion rooted in or primarily relevant to a past historical context.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00a22e32f481909b6006c5b1cdefd3 |
completed | May 10, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a00a1bd9c908190b4aa17a61f48126f |
completed | May 10, 2026, 3:18 p.m. |
Created at: May 3, 2026, 4:01 p.m.