Triple
T25926529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al-Hijr region |
E653319
|
entity |
| Predicate | hasNumberOfMonumentalTombs |
P173199
|
FINISHED |
| Object | over 100 |
—
|
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: over 100 | Statement: [Al-Hijr region, hasNumberOfMonumentalTombs, over 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfMonumentalTombs Context triple: [Al-Hijr region, hasNumberOfMonumentalTombs, over 100]
-
A.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
-
B.
hasMortuaryTemple
Indicates that a person, ruler, or deity is associated with or honored by a specific mortuary temple built for their funerary or commemorative purposes.
-
C.
hasMausoleum
Indicates that one entity possesses, contains, or is associated with a mausoleum dedicated to another entity.
-
D.
isOneOfEarliestTombsIn
Indicates that a tomb belongs to the earliest group of tombs known or constructed within a specified place or context.
-
E.
hasBurialMonumentType
Indicates that an entity is associated with a burial whose monument is of a specified type.
- F. None of above. chosen
Provenance (4 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 22, 2026, 8:35 a.m.