Triple
T20013501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E Ala E |
E494649
|
entity |
| Predicate | hasContemporaryInfluences |
P138377
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [E Ala E, hasContemporaryInfluences, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasContemporaryInfluences Context triple: [E Ala E, hasContemporaryInfluences, yes]
-
A.
hasNotableContemporary
Indicates that one entity is recognized as a significant or prominent contemporary (living or active in the same period) of another entity.
-
B.
modernInfluence
Indicates that one entity has a shaping or impactful effect on another within a contemporary or current context.
-
C.
influencedByCurrent
Indicates that something’s state, behavior, or outcome is affected or determined by the current conditions, context, or situation.
-
D.
hasRetroInfluence
Indicates that something is influenced by or incorporates stylistic or conceptual elements from an earlier time or past era.
-
E.
hasContemporaryRecognition
Indicates that an entity is currently acknowledged, honored, or widely recognized in the present time or modern era.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66238f434819083b11458179bb601 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:34 p.m.