Triple
T25693527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesara |
E644258
|
entity |
| Predicate | fuses |
P158991
|
FINISHED |
| Object | Nagara temple features |
—
|
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: Nagara temple features | Statement: [Vesara, fuses, Nagara temple features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuses Context triple: [Vesara, fuses, Nagara temple features]
-
A.
fuseType
Indicates the specific kind or category of fuse associated with or used in relation to an entity.
-
B.
fires
Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
-
C.
usedFusionFuel
Indicates that an entity employed a specified material or substance as fuel in a fusion process.
-
D.
firing
Indicates initiating the discharge of a weapon or explosive device toward a target.
-
E.
founds
Indicates that an entity establishes or creates an organization, institution, settlement, or similar entity, typically as its originator.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fbc2bcbc81909e16230a8ed01210 |
completed | May 2, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 8:31 p.m.