Triple
T30112877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xuanwei |
E765333
|
entity |
| Predicate | hamNameOrigin |
P3325
|
FINISHED |
| Object | Xuanwei ham named after Xuanwei |
—
|
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: Xuanwei ham named after Xuanwei | Statement: [Xuanwei, hamNameOrigin, Xuanwei ham named after Xuanwei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hamNameOrigin Context triple: [Xuanwei, hamNameOrigin, Xuanwei ham named after Xuanwei]
-
A.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
nameOriginExplanation
Indicates that an explanation is provided for the origin or derivation of a given name.
-
C.
nameEtymologyFor
Indicates that one entity expresses or explains the origin or derivation of the name of another entity.
-
D.
characterNameOrigin
Indicates the source or inspiration from which a character’s name is derived.
-
E.
possibleNameEtymology
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
- 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_69f22475ad7c8190be7f9541044a0bbb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67dc094a081908f4214b878598e54 |
completed | May 2, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:11 p.m.