Triple
T13321336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mysore Palace |
E317320
|
entity |
| Predicate | numberOfBulbsApproximate |
P37175
|
FINISHED |
| Object | thousands of bulbs used for illumination |
—
|
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: thousands of bulbs used for illumination | Statement: [Mysore Palace, numberOfBulbsApproximate, thousands of bulbs used for illumination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfBulbsApproximate Context triple: [Mysore Palace, numberOfBulbsApproximate, thousands of bulbs used for illumination]
-
A.
numberOfLights
chosen
Indicates the quantity of lights associated with or present on a given entity.
-
B.
typeOfLampsUsed
Indicates the specific kinds or categories of lamps that are utilized in a given context or system.
-
C.
hasNumberOfShamashLights
Indicates the relationship specifying how many Shamash (helper) lights are present or associated with an object or setting.
-
D.
hasNumberOfMainLights
Indicates the relationship that specifies how many primary or main lights are associated with an entity.
-
E.
lampPower
Indicates the power rating or electrical wattage associated with a lamp.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.