Triple
T29917447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Dragon Kings |
E759824
|
entity |
| Predicate | hasTempleCult |
P125205
|
FINISHED |
| Object | Dragon King temples |
—
|
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: Dragon King temples | Statement: [Four Dragon Kings, hasTempleCult, Dragon King temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTempleCult Context triple: [Four Dragon Kings, hasTempleCult, Dragon King temples]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
hasCultPlaceType
chosen
Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
-
C.
hasTempleFeature
Indicates that an entity possesses a specific architectural or structural feature characteristic of a temple.
-
D.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
-
E.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 29, 2026, 6:13 p.m.