Triple
T15708779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alamut period |
E380780
|
entity |
| Predicate | hasCenterRegion |
P93967
|
FINISHED |
| Object | northern Iran |
—
|
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: northern Iran | Statement: [Alamut period, hasCenterRegion, northern Iran]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCenterRegion Context triple: [Alamut period, hasCenterRegion, northern Iran]
-
A.
hasCenterIn
chosen
Indicates that something is located, based, or primarily focused within a specified central place or area.
-
B.
hasCenterType
Indicates that something is characterized by or assigned a specific type or category of center.
-
C.
hasRegionalCenterNearby
Indicates that a regional center is located in close proximity to the referenced entity.
-
D.
hasRAndDCenterIn
Indicates that an entity maintains a research and development (R&D) center located in a specified place.
-
E.
hasCenterStatus
Indicates that an entity holds a designated central role, position, or status within a system, organization, or structure.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.