Triple
T35811919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | სომხები |
E1035253
|
entity |
| Predicate | ისტორიული რეგიონი |
P915
|
FINISHED |
| Object | მცირე აზია |
—
|
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: მცირე აზია | Statement: [სომხები, ისტორიული რეგიონი, მცირე აზია]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ისტორიული რეგიონი Context triple: [სომხები, ისტორიული რეგიონი, მცირე აზია]
-
A.
historicalRegion
chosen
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
B.
historicalAdministrativeRegionName
Indicates the name assigned to an administrative region as it existed during a specific historical period.
-
C.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
D.
historicalRegionOfInfluence
Indicates that one entity was historically within the geographic, political, or cultural sphere of influence of another entity.
-
E.
historicalFocusRegion
Indicates that an entity’s primary historical attention, study, or activity is centered on a particular geographic region.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.