Triple
T8887358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince (kōshaku) of the kazoku peerage |
E211565
|
entity |
| Predicate | rankWithinKazoku |
P85550
|
FINISHED |
| Object | highest rank |
—
|
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: highest rank | Statement: [Prince (kōshaku) of the kazoku peerage, rankWithinKazoku, highest rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinKazoku Context triple: [Prince (kōshaku) of the kazoku peerage, rankWithinKazoku, highest rank]
-
A.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
B.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
C.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
-
D.
familyNameIn
Indicates that an entity has a specified family name (surname) in a particular language or cultural context.
-
E.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc618d4c188190810d2e38591f515a |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:53 p.m.