Triple
T33829801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HR 8315 |
E867064
|
entity |
| Predicate | hasChineseAsterism |
P20405
|
FINISHED |
| Object | 壘壁陣 (Lei Bi Zhen) |
—
|
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: 壘壁陣 (Lei Bi Zhen) | Statement: [HR 8315, hasChineseAsterism, 壘壁陣 (Lei Bi Zhen)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChineseAsterism Context triple: [HR 8315, hasChineseAsterism, 壘壁陣 (Lei Bi Zhen)]
-
A.
isAsterismOf
chosen
Indicates that one or more stars collectively form or belong to a specific asterism.
-
B.
isZodiacStar
Indicates that one entity is a zodiac star (or sign) associated with, or characterizing, the other entity.
-
C.
containsAsterism
Indicates that one entity includes or encompasses an asterism (a recognizable pattern or grouping of stars) within its extent or definition.
-
D.
usesConstellation
Indicates that one entity makes use of, relies on, or incorporates a particular constellation in its function, representation, or operation.
-
E.
isOneOfPtolemaicConstellations
Indicates that an entity belongs to the set of constellations originally defined in the Ptolemaic star catalog.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 1, 2026, 1:46 a.m.