Triple
T25232394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nadahabba of Karnataka |
E632248
|
entity |
| Predicate | centerpieceVenue |
P100120
|
FINISHED |
| Object | Mysore Palace |
—
|
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: Mysore Palace | Statement: [Nadahabba of Karnataka, centerpieceVenue, Mysore Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centerpieceVenue Context triple: [Nadahabba of Karnataka, centerpieceVenue, Mysore Palace]
-
A.
heightOfCenterpiece
Indicates the measured vertical height of the centerpiece in the given context or arrangement.
-
B.
visualCenterpiece
Indicates that one entity serves as the primary visual focus or dominant visual element in relation to another entity.
-
C.
decorationCategory
Indicates the classification or type of decoration that an item, element, or space belongs to.
-
D.
homeVenueFocus
Indicates a primary or central emphasis on a particular venue as the main location associated with an entity’s activities or presence.
-
E.
featuresVenue
chosen
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:06 p.m.