Triple
T21607874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kong family |
E533223
|
entity |
| Predicate | hasGenealogy |
P144770
|
FINISHED |
| Object | Kong family genealogy |
—
|
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: Kong family genealogy | Statement: [Kong family, hasGenealogy, Kong family genealogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenealogy Context triple: [Kong family, hasGenealogy, Kong family genealogy]
-
A.
hasGenealogicalInterest
Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage of another entity.
-
B.
hasGenealogicalSignificance
Indicates that something holds importance or relevance within a genealogical or family-lineage context.
-
C.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
D.
hasGenealogicalStudy
Indicates that a subject is associated with or documented in a genealogical study examining familial or ancestral relationships.
-
E.
hasMultipleGenealogies
Indicates that an entity is associated with more than one distinct genealogical lineage or family tree.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e6378881908678dc903b8ba6ac |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:33 p.m.