Triple
T14316322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | marchio Moraviae |
E354964
|
entity |
| Predicate | appliesToPersonType |
P113938
|
FINISHED |
| Object | hereditary prince |
—
|
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: hereditary prince | Statement: [marchio Moraviae, appliesToPersonType, hereditary prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToPersonType Context triple: [marchio Moraviae, appliesToPersonType, hereditary prince]
-
A.
appliesToPerson
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific person.
-
B.
appliedToPersonRole
Indicates that something (such as a rule, condition, or action) is directed toward or relevant for a person specifically in their defined role or capacity.
-
C.
appliesToPartyType
Indicates that a rule, condition, or attribute is relevant to and affects a specific type or category of party (such as an individual, organization, or group).
-
D.
appliesToPersonNationality
Indicates that something is relevant or applicable specifically to a person’s nationality.
-
E.
applicantType
Indicates the classification or category of an applicant in relation to an application or selection process.
- F. None of above. chosen
Provenance (4 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8838e45c819080ee69dd39e3bd43 |
completed | April 14, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69de2a9515f4819081aabf251bca5878 |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e9ded24819099200349cf80e068 |
completed | April 14, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:12 a.m.