Triple
T26061779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaemenid administration |
E657280
|
entity |
| Predicate | usedTerritorialUnit |
P63885
|
FINISHED |
| Object | satrapy |
—
|
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: satrapy | Statement: [Achaemenid administration, usedTerritorialUnit, satrapy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTerritorialUnit Context triple: [Achaemenid administration, usedTerritorialUnit, satrapy]
-
A.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
-
B.
territorialUse
chosen
Indicates the use, control, or occupation of a geographic area or territory by an entity.
-
C.
hasTerritorialAssociation
Indicates a relationship where an entity is linked or connected to a specific territory, area, or geographic region.
-
D.
usedRegion
Indicates that an entity operates in, applies to, or is utilized within a specified geographic or administrative region.
-
E.
usedInDistrict
Indicates that something is utilized, applied, or implemented within the boundaries or jurisdiction of a specific district.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60692a4f081909cd9d0ca75d590a0 |
completed | May 2, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:18 p.m.