Triple
T28244731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishop of Lübeck |
E712131
|
entity |
| Predicate | didNotRule |
P49484
|
FINISHED |
| Object | Free Imperial City of Lübeck |
—
|
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: Free Imperial City of Lübeck | Statement: [Prince-Bishop of Lübeck, didNotRule, Free Imperial City of Lübeck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotRule Context triple: [Prince-Bishop of Lübeck, didNotRule, Free Imperial City of Lübeck]
-
A.
didNotOverrule
Indicates that one entity, typically a higher authority or court, chose not to overturn, reverse, or invalidate the decision or ruling made by another entity.
-
B.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
C.
didNotBecome
chosen
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
doesNotBan
Indicates that one entity allows or permits another entity or action by explicitly not prohibiting it.
- 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c84f1c8190879e643c18e74e75 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 11 p.m.