Triple
T33946796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iram dhāt al-‘imād |
E870311
|
entity |
| Predicate | modernInterest |
P192862
|
FINISHED |
| Object | subject of lost city theories |
—
|
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: subject of lost city theories | Statement: [Iram dhāt al-‘imād, modernInterest, subject of lost city theories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernInterest Context triple: [Iram dhāt al-‘imād, modernInterest, subject of lost city theories]
-
A.
historicalInterest
Indicates that one entity has a notable relevance, appeal, or significance to the study or understanding of the past.
-
B.
modernInfluence
Indicates that one entity has a shaping or impactful effect on another within a contemporary or current context.
-
C.
historicallyRich
Indicates that an entity possesses significant historical depth, importance, or a wealth of notable past events and heritage.
-
D.
modernIssue
Indicates that the subject is a contemporary or current-day issue affecting the object or broader context.
-
E.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: May 1, 2026, 1:49 a.m.