Triple
T24123574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyeongju Kim clan |
E597729
|
entity |
| Predicate | hasNotableAncestralSeat |
P10501
|
FINISHED |
| Object | Gyeongju |
—
|
NE NERFINISHED |
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: Gyeongju | Statement: [Gyeongju Kim clan, hasNotableAncestralSeat, Gyeongju]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAncestralSeat Context triple: [Gyeongju Kim clan, hasNotableAncestralSeat, Gyeongju]
-
A.
formerFamilySeat
Indicates that a location was previously the principal residence or ancestral home of a particular family but no longer holds that status.
-
B.
hasAncestralResidence
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
C.
hasNotableDynastyMember
Indicates that a dynasty includes at least one member who is historically or culturally notable.
-
D.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
E.
nobleFamilySeat
chosen
Indicates the location that serves as the principal seat or main residence of a noble family.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee718f88190860d40c6f09a77c8 |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.