Triple
T28947898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayrarat |
E730928
|
entity |
| Predicate | namedInSource |
P35337
|
FINISHED |
| Object | Ashkharatsuyts |
—
|
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: Ashkharatsuyts | Statement: [Ayrarat, namedInSource, Ashkharatsuyts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedInSource Context triple: [Ayrarat, namedInSource, Ashkharatsuyts]
-
A.
namedIn
chosen
Indicates that one entity is explicitly mentioned or referenced by name within another entity (such as a document, statement, or record).
-
B.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
C.
namedInContextOf
Indicates that an entity is mentioned or identified specifically within a particular context, situation, or frame of reference.
-
D.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
-
E.
namedWithin
Indicates that one entity is given a specific name or designation within the scope, context, or boundaries of another 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 28, 2026, 8:41 a.m.