Triple
T37391465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periyanayaki |
E928721
|
entity |
| Predicate | principalConsortAt |
P184933
|
FINISHED |
| Object | Nageswaran Temple |
—
|
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: Nageswaran Temple | Statement: [Periyanayaki, principalConsortAt, Nageswaran Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalConsortAt Context triple: [Periyanayaki, principalConsortAt, Nageswaran Temple]
-
A.
principalConductor
Indicates that one entity serves as the main or lead conductor for another entity, typically an orchestra or musical ensemble.
-
B.
oneOfPrincipalConsortsOf
chosen
Indicates that the subject is one of several principal consorts (primary spouses or partners) of the object.
-
C.
notableConsort
Indicates that one entity is a spouse or consort of another who is notable or significant in some recognized context.
-
D.
principalAct
Indicates that an entity performs or is responsible for the main or primary action in a given context.
-
E.
principalKamiOf
Indicates that one entity serves as the primary or chief kami (deity/spirit) associated with another entity, such as a place, shrine, or group.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.