Triple
T31925311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruno I, Count of Brunswick |
E815086
|
entity |
| Predicate | government system |
P220
|
FINISHED |
| Object | feudalism |
—
|
LITERAL FINISHED |
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: feudalism | Statement: [Bruno I, Count of Brunswick, government system, feudalism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: government system Context triple: [Bruno I, Count of Brunswick, government system, feudalism]
-
A.
politicalFramework
Indicates the overarching system of political structures, principles, and rules that organize and govern relationships and decision-making within a society or institution.
-
B.
government1
Indicates that one entity functions as the governing authority or administration over another entity.
-
C.
associatedPoliticalSystem
Indicates that there exists a political system with which the subject is formally or conceptually connected.
-
D.
government2
Indicates a relationship where an entity serves as or functions as the governing authority or administrative body over another entity.
-
E.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: May 1, 2026, 12:03 a.m.