Triple
T35811950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | სომხები |
E1035253
|
entity |
| Predicate | ისტორიული ქრონიკები |
P95967
|
FINISHED |
| Object | მოვსეს ხორენაცი |
—
|
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: მოვსეს ხორენაცი | Statement: [სომხები, ისტორიული ქრონიკები, მოვსეს ხორენაცი]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ისტორიული ქრონიკები Context triple: [სომხები, ისტორიული ქრონიკები, მოვსეს ხორენაცი]
-
A.
historicalWork
Indicates that one entity is a work (such as a document, artifact, or creation) that originates from or pertains to a past historical period in relation to another entity.
-
B.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
C.
الأصل التاريخي
Indicates the historical origin or source from which something or someone is derived.
-
D.
historicalNarrative
chosen
Indicates that one entity presents or constitutes a story or account about past events involving another entity.
-
E.
الدور التاريخي
Indicates the historical role or function that an entity has played within a particular period, context, or sequence of events.
- 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_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:06 p.m.