Triple
T1517828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thatta |
E32159
|
entity |
| Predicate | ShahJahanMosqueCompletionYear |
P23507
|
FINISHED |
| Object | 1647 |
—
|
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: 1647 | Statement: [Thatta, ShahJahanMosqueCompletionYear, 1647]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ShahJahanMosqueCompletionYear Context triple: [Thatta, ShahJahanMosqueCompletionYear, 1647]
-
A.
reconvertedToMosqueBy
Indicates that a building or site, previously used for another purpose, was changed back into a mosque by a specific agent or authority.
-
B.
lastMajorTempleClosed
Indicates the time or event at which the final significant temple associated with an entity was permanently closed.
-
C.
dateOfMainRoyalMonument
chosen
Indicates the date on which a person's principal royal monument (such as a main tomb or commemorative structure) was established, completed, or formally dedicated.
-
D.
dateOfShahDeparture
Indicates the date on which the Shah left or departed from a particular place or position.
-
E.
functionEndAsMosqueFirstPeriod
Indicates that the entity’s function as a mosque ended during the first defined historical period.
- 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_69a885e8caf88190a5fbb6159ce87786 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9396e16408190b5e7b0ac43376d81 |
completed | March 5, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69a907aa67cc81909f00135365447399 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.