Triple
T9649269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back to the Egg |
E233290
|
entity |
| Predicate | includesInfluence |
P69465
|
FINISHED |
| Object | new wave |
—
|
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: new wave | Statement: [Back to the Egg, includesInfluence, new wave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesInfluence Context triple: [Back to the Egg, includesInfluence, new wave]
-
A.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
B.
influentialFrom
chosen
Indicates that one entity has exerted influence on another, contributing to or shaping the latter’s ideas, behavior, or development.
-
C.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
-
D.
hasPossibleInfluence
Indicates that one entity may have an effect on, contribute to, or shape the state, behavior, or outcome of another entity, without asserting that this influence is definite or direct.
-
E.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
- 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_69ca848b31648190b57aa55da20285be |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9badd630819087fd844d7878ec61 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:13 p.m.