Triple
T21882786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cesaro |
E540329
|
entity |
| Predicate | strengthFeat |
P146027
|
FINISHED |
| Object | giant swing on large opponents |
—
|
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: giant swing on large opponents | Statement: [Cesaro, strengthFeat, giant swing on large opponents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthFeat Context triple: [Cesaro, strengthFeat, giant swing on large opponents]
-
A.
strengthDescription
Indicates a description or characterization of the degree of strength associated with an entity or relationship.
-
B.
strengthType
Indicates the specific category or nature of strength associated with an entity or relationship (e.g., physical, structural, or conceptual strength).
-
C.
strength
Indicates the degree of power, intensity, or effectiveness with which an entity can act on, influence, or withstand another entity or force.
-
D.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
-
E.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
- 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_69e0c479a98081908ce333853fdd4348 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f118e890088190aa3023c78a99a536 |
completed | April 28, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69e6be9a65888190a66598d62d20366c |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 7:05 p.m.