Triple
T15878265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baha al-Din Sam I |
E385004
|
entity |
| Predicate | realmCoreArea |
P58897
|
FINISHED |
| Object | central Afghanistan |
—
|
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: central Afghanistan | Statement: [Baha al-Din Sam I, realmCoreArea, central Afghanistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmCoreArea Context triple: [Baha al-Din Sam I, realmCoreArea, central Afghanistan]
-
A.
coreAreaOf
chosen
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
B.
realmWithin
Indicates that one realm or domain is contained inside, or exists as a subset of, another realm or domain.
-
C.
coreZoneArea
Indicates the area or spatial extent of a designated core zone within a larger region or system.
-
D.
coreAreaCharacteristic
Indicates that a characteristic or feature is specifically associated with the core area of something, rather than its peripheral or secondary parts.
-
E.
venueArea
Indicates the physical size or spatial extent of a venue, typically measured in units such as square meters or square feet.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.