Triple
T17775444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hsia-men |
E443754
|
entity |
| Predicate | meaningOfCharacters |
P64570
|
FINISHED |
| Object | “mansion gate” |
—
|
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: “mansion gate” | Statement: [Hsia-men, meaningOfCharacters, “mansion gate”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfCharacters Context triple: [Hsia-men, meaningOfCharacters, “mansion gate”]
-
A.
associatedCharacterMeaning
Indicates that there is a relationship between a character and the meaning, interpretation, or concept that this character is intended to represent.
-
B.
associatedGlyphMeaning
chosen
Indicates a relationship where a glyph is linked to, or represents, a particular meaning or semantic value.
-
C.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
D.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
E.
chantMeaning
Indicates that an entity performs or conveys the meaning or content of a chant in relation to another entity or context.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4871c23408190aae7f1a2c77a10cb |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.