Triple
T27086922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greco-Roman |
E686059
|
entity |
| Predicate | emphasizesClinchWork |
P162047
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Greco-Roman, emphasizesClinchWork, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesClinchWork Context triple: [Greco-Roman, emphasizesClinchWork, true]
-
A.
emphasizesConsonanceOf
Indicates that one entity highlights, stresses, or draws attention to the harmony, agreement, or consonant relationship between itself and another entity.
-
B.
emphasizesAbility
Indicates that one entity highlights, stresses, or draws special attention to the capability or skill of another entity.
-
C.
closingEmphasis
Indicates that one entity concludes or reinforces another entity’s point, action, or message with particular stress or importance.
-
D.
concentrates
Indicates that one entity directs its attention, effort, or resources intensely toward a specific target, task, or area.
-
E.
skillEmphasis
Indicates that a particular skill is given special focus, priority, or importance within a context such as a role, task, or curriculum.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6234735cc819097c3f109e724b0a4 |
completed | May 2, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 8:38 a.m.