Triple
T25860177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agyrium |
E651457
|
entity |
| Predicate | laterHellenizedBy |
P175950
|
FINISHED |
| Object | Greeks |
—
|
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: Greeks | Statement: [Agyrium, laterHellenizedBy, Greeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterHellenizedBy Context triple: [Agyrium, laterHellenizedBy, Greeks]
-
A.
laterSyncretizedWith
Indicates that one element was subsequently merged or conflated with another into a single, combined form or identity.
-
B.
laterNamed
Indicates that an entity was given a new name at a later time, linking its original identity to its subsequent name.
-
C.
laterBecameKnownAs
Indicates that an entity was previously known by one name or identity and, at a later time, came to be known by a different name or identity.
-
D.
laterRomanizedInto
Indicates that an entity’s original form (such as a name, word, or title) was subsequently converted into a later Romanized (Latin-script) version.
-
E.
laterTranslatedAs
Indicates that something was translated at a later time into a different language, form, or version under a specified title or expression.
- F. None of above. chosen
Provenance (4 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 22, 2026, 8:05 a.m.