Triple
T28549015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Let's Celebrate!" |
E722827
|
entity |
| Predicate | containsVerb |
P46221
|
FINISHED |
| Object | celebrate |
—
|
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: celebrate | Statement: ["Let's Celebrate!", containsVerb, celebrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsVerb Context triple: ["Let's Celebrate!", containsVerb, celebrate]
-
A.
hasComponentVerb
Indicates that an expression or construction includes a specific verb as one of its constituent components.
-
B.
hasVerbClass
Indicates that an action or event is categorized into a specific verb class based on its grammatical or semantic behavior.
-
C.
hasVerbAspect
Indicates that a verb or verbal expression is associated with a particular grammatical aspect (such as perfective, imperfective, or progressive) describing the temporal structure of the action or state.
-
D.
titleContainsVerb
chosen
Indicates that the title of an entity includes at least one verb within its text.
-
E.
hasVerbSystemFrom
Indicates that one language or linguistic system derives or adopts its verb system from another source language or system.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 28, 2026, 3:41 a.m.