Triple
T4759925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iota |
E105674
|
entity |
| Predicate | IPAValueAncientGreek |
P58357
|
FINISHED |
| Object | /i/ or /iː/ depending on period |
—
|
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: /i/ or /iː/ depending on period | Statement: [Iota, IPAValueAncientGreek, /i/ or /iː/ depending on period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IPAValueAncientGreek Context triple: [Iota, IPAValueAncientGreek, /i/ or /iː/ depending on period]
-
A.
numericValueInGreekNumerals
Indicates that a given numeric value is represented or expressed using Greek numeral notation.
-
B.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
C.
hasNameInGreek
Indicates that an entity is associated with a specific representation of its name in the Greek language.
-
D.
typeOfGreek
Indicates that one entity is a specific kind or category of Greek associated with the other entity.
-
E.
hasGreekCounterpartGroup
Indicates that something is associated with a corresponding group or set of counterparts in the context of Greek tradition or classification.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650dc7fc81909b483ef3c456ae0d |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.