Triple
T34681824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xin |
E890640
|
entity |
| Predicate | hasVariantTranscription |
P35086
|
FINISHED |
| Object | Hsin |
—
|
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: Hsin | Statement: [Xin, hasVariantTranscription, Hsin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVariantTranscription Context triple: [Xin, hasVariantTranscription, Hsin]
-
A.
hasVariantReadingsWith
Indicates a relationship where two textual items are linked because they exhibit differing or alternative readings of (typically) the same underlying content.
-
B.
hasVariantSpelling
Indicates that one term is an alternative spelling form of another term.
-
C.
hasVariantWithoutToneMarks
Indicates that one textual form is a variant of another in which all tone marks have been removed.
-
D.
hasAlternativeVocalization
chosen
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
E.
hasVariantText
Indicates that an entity is associated with an alternative or differing textual form of its content.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232925e48190b6ecd37927325057 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.