Triple
T11703988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abov |
E278194
|
entity |
| Predicate | hasMedievalAssociation |
P46137
|
FINISHED |
| Object | nobility of the Kingdom of Hungary |
—
|
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: nobility of the Kingdom of Hungary | Statement: [Abov, hasMedievalAssociation, nobility of the Kingdom of Hungary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedievalAssociation Context triple: [Abov, hasMedievalAssociation, nobility of the Kingdom of Hungary]
-
A.
isMedieval
Indicates that something belongs to, originates from, or is characteristic of the medieval (Middle Ages) period.
-
B.
hasMedievalElements
Indicates that something incorporates characteristics, motifs, or features typical of the medieval period.
-
C.
medievalStatus
chosen
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
D.
medievalSeeTransferredTo
Indicates that authority, ownership, or jurisdiction over a medieval ecclesiastical see was formally transferred from one holder or location to another.
-
E.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49b1080819096593733ee48a187 |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:40 p.m.