Triple
T33486234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hassan Mosque |
E857617
|
entity |
| Predicate | minaretHeightPlanned |
P16755
|
FINISHED |
| Object | approximately 80–86 metres |
—
|
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: approximately 80–86 metres | Statement: [Hassan Mosque, minaretHeightPlanned, approximately 80–86 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minaretHeightPlanned Context triple: [Hassan Mosque, minaretHeightPlanned, approximately 80–86 metres]
-
A.
hasMinaretHeightApprox
chosen
Indicates that an entity has a minaret whose height is approximately a specified value, allowing for some margin of imprecision.
-
B.
minaretAdded
Indicates that a minaret has been constructed and incorporated into an existing structure or site.
-
C.
minaretBuiltBy
Indicates that a minaret was constructed by a particular agent, such as a person, group, or organization.
-
D.
minaretCondition
Indicates the physical state, integrity, or preservation status of a minaret in relation to a specified point in time or event.
-
E.
minaretShape
Indicates that one entity has the specified architectural shape or form of a minaret in relation to another entity.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e533a2b88190a9015009c6d69696 |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.