Triple
T10703079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theophania |
E252326
|
entity |
| Predicate | meaningOfComponent:phaino |
P95364
|
FINISHED |
| Object | to appear |
—
|
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: to appear | Statement: [Theophania, meaningOfComponent:phaino, to appear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfComponent:phaino Context triple: [Theophania, meaningOfComponent:phaino, to appear]
-
A.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
B.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
C.
demonstratedPhenomenon
Indicates that an entity has shown, exhibited, or provided evidence for the occurrence of a particular phenomenon.
-
D.
describesPremiseOf
Indicates that one entity expresses, explains, or sets out the foundational idea, situation, or assumption underlying another entity.
-
E.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fddd28d481908abc5c1d4e5a9f3e |
completed | April 9, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8ea6408190a800f9cb57372189 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:12 p.m.