Triple
T36530794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jin |
E900436
|
entity |
| Predicate | meaningVariesWith |
P36743
|
FINISHED |
| Object | chosen hanja characters |
—
|
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: chosen hanja characters | Statement: [Jin, meaningVariesWith, chosen hanja characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningVariesWith Context triple: [Jin, meaningVariesWith, chosen hanja characters]
-
A.
usageVariesBy
Indicates that the way something is used differs depending on a specified factor, such as context, user, location, or conditions.
-
B.
varies
Indicates that the value, state, or condition of one entity changes in response to differences in another entity or context.
-
C.
termVariesBy
chosen
Indicates that the value or meaning of a term changes depending on a specified factor, such as context, dimension, or condition.
-
D.
viewVariesAmong
Indicates that the way something is viewed, perceived, or interpreted differs across multiple entities or contexts.
-
E.
variesOver
Indicates that the value, state, or behavior of one entity changes as a function of another entity or parameter.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.