Triple
T6818451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiāntán |
E156830
|
entity |
| Predicate | shapeSymbolism |
P73239
|
FINISHED |
| Object | circular heavens and square earth |
—
|
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: circular heavens and square earth | Statement: [Tiāntán, shapeSymbolism, circular heavens and square earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shapeSymbolism Context triple: [Tiāntán, shapeSymbolism, circular heavens and square earth]
-
A.
emblemSymbolism
Indicates that one entity serves as an emblem whose design or features symbolically represent or convey meanings about another entity.
-
B.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
C.
starColorSymbolism
Indicates how the color of a star is associated with particular symbolic meanings or themes.
-
D.
typicalMaterialSymbolism
Indicates that a material is commonly or characteristically used to symbolize or represent something in a given cultural or contextual setting.
-
E.
starMeaning
Indicates that one entity represents or conveys the symbolic or interpretive significance of a star associated with another entity.
- F. None of above. chosen
Provenance (4 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d355b52081909f037cec76bdccf6 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:17 p.m.