Triple
T38079353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangmu Tianwang |
E950808
|
entity |
| Predicate | directionSymbolism |
P30236
|
FINISHED |
| Object | west |
—
|
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: west | Statement: [Guangmu Tianwang, directionSymbolism, west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionSymbolism Context triple: [Guangmu Tianwang, directionSymbolism, west]
-
A.
languageOfSymbolism
Indicates that one entity is the language in which the symbolic meaning or symbolism of another entity is expressed or encoded.
-
B.
orientationMeaning
Indicates the conceptual or semantic interpretation associated with a particular orientation or directional arrangement between entities.
-
C.
shapeSymbolism
Indicates how a particular shape is associated with or conveys symbolic meaning within a given context.
-
D.
directionalDesignation
chosen
Indicates a relationship where one entity is assigned or labeled with a specific directional orientation relative to another entity or reference frame.
-
E.
fieldSymbolism
Indicates the symbolic meaning or thematic associations that a field (as a setting, area, or domain) conveys within a given 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 4:21 p.m.