Triple
T5089388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ehoiai |
E114715
|
entity |
| Predicate | hasOpeningFormula |
P3660
|
FINISHED |
| Object | ἢ οἵη (ē hoiē) |
—
|
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: ἢ οἵη (ē hoiē) | Statement: [Ehoiai, hasOpeningFormula, ἢ οἵη (ē hoiē)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpeningFormula Context triple: [Ehoiai, hasOpeningFormula, ἢ οἵη (ē hoiē)]
-
A.
hasOpeningType
Indicates that one entity has, features, or is characterized by a particular type or kind of opening.
-
B.
hasOpeningFeature
Indicates that an entity possesses a specific characteristic, element, or attribute related to its opening or entry point.
-
C.
hasFormulation
chosen
Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
-
D.
hasOpeningDeclaredBy
Indicates that the opening or initial state of something is formally specified or announced by a particular agent or authority.
-
E.
hasFormulationPeriod
Indicates the time span during which something is planned, designed, or developed before it is finalized or implemented.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd753f6544819090c028b34ee87536 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.