Triple
T26641709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tashiding Monastery |
E668796
|
entity |
| Predicate | BumchuHeldOn |
P161081
|
FINISHED |
| Object | first lunar month of Tibetan calendar |
—
|
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: first lunar month of Tibetan calendar | Statement: [Tashiding Monastery, BumchuHeldOn, first lunar month of Tibetan calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BumchuHeldOn Context triple: [Tashiding Monastery, BumchuHeldOn, first lunar month of Tibetan calendar]
-
A.
WestStartingGuard
Indicates that an entity serves as the starting guard for a team representing the Western side (e.g., in an all-star or conference-based matchup).
-
B.
MegaCharizardYType
Indicates that an entity has the Pokémon type(s) associated specifically with Mega Charizard Y.
-
C.
MegaCharizardXType
Indicates that an entity has the Pokémon type configuration associated specifically with Mega Charizard X.
-
D.
ownsPokémon
Indicates that one entity possesses or has ownership of a particular Pokémon.
-
E.
enemySpecies
Indicates that two species are in an antagonistic or hostile relationship, typically viewing each other as enemies.
- 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_69ee9d0024b8819090a7c8cf669a3b6c |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616320b9c8190b3a5792ffcfe3bc1 |
completed | May 2, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60f24ed608190bffe6c6084fc2f7a |
completed | May 2, 2026, 2:50 p.m. |
Created at: April 27, 2026, 2:29 a.m.