Triple
T7123803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Ranganathaswamy Temple, Srirangam |
E166009
|
entity |
| Predicate | hasEnclosureName |
P74990
|
FINISHED |
| Object | prakarams |
—
|
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: prakarams | Statement: [Sri Ranganathaswamy Temple, Srirangam, hasEnclosureName, prakarams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnclosureName Context triple: [Sri Ranganathaswamy Temple, Srirangam, hasEnclosureName, prakarams]
-
A.
hasCoverName
Indicates that one entity uses or is known by an alternative, often secret or assumed, name in relation to another entity or context.
-
B.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
-
C.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
D.
hasPackageName
Indicates that an entity (such as a software component or module) is associated with a specific package name identifier.
-
E.
hasSecurityName
Indicates that an entity is associated with a specific security-related name or identifier (e.g., the official name of a security or protected resource).
- 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e64ab1f881908bc2468cc72d2544 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:44 p.m.