Triple
T27244905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekhoni |
E687313
|
entity |
| Predicate | hasRealisticStyle |
P197386
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ekhoni, hasRealisticStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRealisticStyle Context triple: [Ekhoni, hasRealisticStyle, true]
-
A.
usesRealisticSetting
Indicates that an event, narrative, or representation takes place within a setting that closely resembles real-world environments, conditions, or contexts.
-
B.
hasStyleCharacteristics
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
-
C.
hasRealModel
Indicates that an abstract, theoretical, or simplified entity is associated with a corresponding concrete or physically instantiated model in the real world.
-
D.
hasTheatricalStyle
Indicates that one entity possesses, exhibits, or is characterized by a particular theatrical style associated with another entity.
-
E.
hasMinimalistStyle
Indicates that something exhibits a simple, clean, and uncluttered style with minimal decorative elements.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
| PDg | Predicate description generation | batch_69fe8f730bb88190975bffd49f5e0f3b |
completed | May 9, 2026, 1:35 a.m. |
Created at: April 27, 2026, 10:40 a.m.