Triple
T34050295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whoa |
E873204
|
entity |
| Predicate | helpedElevate |
P33868
|
FINISHED |
| Object | Snoh Aalegra global recognition |
—
|
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: Snoh Aalegra global recognition | Statement: [Whoa, helpedElevate, Snoh Aalegra global recognition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedElevate Context triple: [Whoa, helpedElevate, Snoh Aalegra global recognition]
-
A.
helpedCause
chosen
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
B.
laterHelps
Indicates that one entity provides help or assistance to another at a subsequent time rather than immediately.
-
C.
elevatedTo
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
D.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
E.
raisedWith
Indicates that two or more entities grew up together in the same household or close environment during their formative years.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.