Triple
T33735870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naga fireball festival |
E864411
|
entity |
| Predicate | viewedAsByLocals |
P21336
|
FINISHED |
| Object | sign of Naga paying homage to Buddha |
—
|
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: sign of Naga paying homage to Buddha | Statement: [Naga fireball festival, viewedAsByLocals, sign of Naga paying homage to Buddha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewedAsByLocals Context triple: [Naga fireball festival, viewedAsByLocals, sign of Naga paying homage to Buddha]
-
A.
representedLocallyBy
Indicates that an entity is expressed, implemented, or instantiated in a specific local form or representation by another entity.
-
B.
viewsAs
Indicates that one entity perceives, interprets, or regards another entity in a particular way or role.
-
C.
viewedBySomeAs
chosen
Indicates that at least one observer or group perceives or interprets an entity in a particular way or role.
-
D.
viewedBy
Indicates that something has been seen, observed, or watched by a particular entity.
-
E.
viewsClientAs
Indicates that one entity regards or treats another entity as a client within a service, business, or professional relationship.
- 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:44 a.m.