Triple
T10480282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hassan Mosque complex |
E247151
|
entity |
| Predicate | intendedMinaretHeight |
P16755
|
FINISHED |
| Object | approximately 44 meters (Hassan Tower) |
—
|
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 44 meters (Hassan Tower) | Statement: [Hassan Mosque complex, intendedMinaretHeight, approximately 44 meters (Hassan Tower)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedMinaretHeight Context triple: [Hassan Mosque complex, intendedMinaretHeight, approximately 44 meters (Hassan Tower)]
-
A.
hasMinaretHeightApprox
chosen
Indicates that an entity has a minaret whose height is approximately a specified value, allowing for some margin of imprecision.
-
B.
floorCountOfMinaret
Indicates the number of floors or levels that a minaret has.
-
C.
numberOfBalconiesOnMinarets
Indicates the count of balconies present on the minarets associated with a given subject.
-
D.
hasMinarets
Indicates that an entity (typically a building) possesses one or more minarets as architectural features.
-
E.
minaretCondition
Indicates the physical state, integrity, or preservation status of a minaret in relation to a specified point in time or event.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5095b2ec881909e1220d83e750a75 |
completed | April 7, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:22 p.m.