Triple
T27402573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cia-Cia people |
E691892
|
entity |
| Predicate | writingSystemExperimentPartner |
P163263
|
FINISHED |
| Object | Hunminjeongeum Society |
—
|
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: Hunminjeongeum Society | Statement: [Cia-Cia people, writingSystemExperimentPartner, Hunminjeongeum Society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingSystemExperimentPartner Context triple: [Cia-Cia people, writingSystemExperimentPartner, Hunminjeongeum Society]
-
A.
writingSystemCreator
Indicates that one entity is the creator or originator of the writing system used by another entity.
-
B.
writingPartner
Indicates a collaborative relationship in which two or more entities work together as co-authors or co-writers on written material.
-
C.
writingSystemScope
Indicates the range or extent of content, languages, or contexts to which a particular writing system applies or is used.
-
D.
contentPartner
Indicates a relationship in which one entity collaborates with another to create, supply, or distribute content.
-
E.
writingSystemUsedIn
Indicates that a particular writing system is employed for written communication within a given language, region, or context.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6369a22688190a5674191c90a5d12 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 12:29 p.m.