Triple
T14249252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H.I.H. |
E353213
|
entity |
| Predicate | addressesRank |
P113396
|
FINISHED |
| Object | imperial family member |
—
|
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: imperial family member | Statement: [H.I.H., addressesRank, imperial family member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesRank Context triple: [H.I.H., addressesRank, imperial family member]
-
A.
areaRank
Indicates the relative ordering or position of an entity based on the size of its area compared to others.
-
B.
rankByProminence
Indicates that entities are ordered or assigned a position based on their level of prominence or notability relative to one another.
-
C.
portRank
Indicates the relative importance or hierarchical ranking assigned to a port within a given system or context.
-
D.
countyRank
Indicates the relative position or standing of a county within a larger ordered set, typically based on some quantitative measure such as size, population, or performance.
-
E.
populationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6295ef9081909cfb0c1283bca21a |
completed | April 14, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69de05c09b7881908acbca18bd7d997c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239bd0f48190ada38c0261e0ef3c |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:08 a.m.