Triple
T22868362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aghvank |
E567118
|
entity |
| Predicate | hadScript |
P41683
|
FINISHED |
| Object | Albanian script |
—
|
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: Albanian script | Statement: [Aghvank, hadScript, Albanian script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadScript Context triple: [Aghvank, hadScript, Albanian script]
-
A.
hasNotableScript
chosen
Indicates that an entity is associated with a script (such as a writing system or screenplay) that is considered notable or significant.
-
B.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
C.
hasScriptedNature
Indicates that something is predetermined or follows a written or planned script rather than occurring spontaneously.
-
D.
hadURL
Indicates that an entity was associated with or linked to a specific URL at some point in time.
-
E.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f02c8b8819095cbee626f935fed |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d8c0608190afef4c4e530c0e2c |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.