Triple
T25230655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Lord Ananta |
E632210
|
entity |
| Predicate | notableFeatureOfReferent |
P61000
|
FINISHED |
| Object | historic Sree Padmanabhaswamy 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: historic Sree Padmanabhaswamy Temple | Statement: [City of Lord Ananta, notableFeatureOfReferent, historic Sree Padmanabhaswamy Temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeatureOfReferent Context triple: [City of Lord Ananta, notableFeatureOfReferent, historic Sree Padmanabhaswamy Temple]
-
A.
notableFeatureOn
chosen
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
B.
notableFeatureInStory
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
-
C.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
D.
notableTechnicalFeature
Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
-
E.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 21, 2026, 1:04 p.m.