Triple
T4759916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iota |
E105674
|
entity |
| Predicate | historicallyRepresented |
P58355
|
FINISHED |
| Object | short i sound |
—
|
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: short i sound | Statement: [Iota, historicallyRepresented, short i sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyRepresented Context triple: [Iota, historicallyRepresented, short i sound]
-
A.
historicalRepresentative
Indicates that one entity serves or served as an official representative or delegate of another entity in a historical context.
-
B.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
C.
historicallyDocumentedBy
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
-
D.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
E.
historicallyGivenIn
Indicates that something was customarily or traditionally granted, presented, or assigned to something or someone in the past.
- 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.