Triple
T24437687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thurn und Taxis family |
E616168
|
entity |
| Predicate | postalMonopoly |
P60975
|
FINISHED |
| Object | Imperial Reichspost |
—
|
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: Imperial Reichspost | Statement: [Thurn und Taxis family, postalMonopoly, Imperial Reichspost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postalMonopoly Context triple: [Thurn und Taxis family, postalMonopoly, Imperial Reichspost]
-
A.
monopolyOn
Indicates that one entity has exclusive control or rights over a resource, market, or activity, preventing others from participating on equal terms.
-
B.
isMonopoly
Indicates that one entity exclusively controls a market or resource, facing no significant competition.
-
C.
monopolySide
Indicates that one party holds exclusive or dominant control in a market or domain relative to the other party.
-
D.
monopolyPrice
Indicates that the price is set by a single dominant seller with exclusive control over the market, rather than by competitive market forces.
-
E.
monopolyGrantedBy
chosen
Indicates that one party has been given exclusive control or rights over a market, resource, or activity by another authority or 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297881fa08190b82bdc5ebeae96f7 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.