Triple
T28496674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagar |
E721123
|
entity |
| Predicate | wasRegionalCenterFor |
P117896
|
FINISHED |
| Object | Khabur plains |
—
|
NE NERFINISHED |
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: Khabur plains | Statement: [Nagar, wasRegionalCenterFor, Khabur plains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRegionalCenterFor Context triple: [Nagar, wasRegionalCenterFor, Khabur plains]
-
A.
hadRegionalCenter
Indicates that an entity possessed, operated, or was associated with a specific regional center serving a defined geographic area.
-
B.
servesAsRegionalCenterFor
chosen
Indicates that one entity functions as the primary administrative, economic, or service hub for a surrounding region or group of entities.
-
C.
isScientificCenterFor
Indicates that one entity serves as a primary location or institution dedicated to conducting, coordinating, or supporting scientific research, education, or activities related to another entity.
-
D.
hasRegionCenter
Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
-
E.
hasRegionalCenterNearby
Indicates that a regional center is located in close proximity to the referenced entity.
- 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_69f01a5afdac8190ac6e72d5c100bd58 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:04 a.m.