Triple
T25711806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clara Eißner |
E644751
|
entity |
| Predicate | proposedAtPlace |
P42733
|
FINISHED |
| Object | Copenhagen |
—
|
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: Copenhagen | Statement: [Clara Eißner, proposedAtPlace, Copenhagen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedAtPlace Context triple: [Clara Eißner, proposedAtPlace, Copenhagen]
-
A.
proposedInCity
chosen
Indicates that something, such as a plan, project, or idea, was formally proposed within a particular city.
-
B.
locationProposedFrom
Indicates a proposed or suggested origin location from which something is expected or planned to come.
-
C.
proposedInContextOf
Indicates that something (such as an idea, action, or change) was proposed specifically within, and in relation to, a particular situation, setting, or surrounding circumstances.
-
D.
posedAt
Indicates that something (such as a question, challenge, or problem) is directed toward or presented to a particular target or context.
-
E.
decisionPlace
Indicates the location where a decision is made or formally determined.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 21, 2026, 9:16 p.m.