Triple
T37493276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John II, Margrave of Brandenburg |
E931754
|
entity |
| Predicate | coRuled |
P13111
|
FINISHED |
| Object | Margraviate of Brandenburg |
—
|
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: Margraviate of Brandenburg | Statement: [John II, Margrave of Brandenburg, coRuled, Margraviate of Brandenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRuled Context triple: [John II, Margrave of Brandenburg, coRuled, Margraviate of Brandenburg]
-
A.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
-
B.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
C.
providedRulerFor
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
-
D.
coRuledTerritoryWith
Indicates that two or more rulers shared authority over the same territory during an overlapping period of rule.
-
E.
coRulerWith
chosen
Indicates that two or more entities share ruling authority over the same domain or polity at the same time.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.