Triple
T36042185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cecil Vyse |
E1042570
|
entity |
| Predicate | engagementHighlights |
P184503
|
FINISHED |
| Object | class tensions |
—
|
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: class tensions | Statement: [Cecil Vyse, engagementHighlights, class tensions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementHighlights Context triple: [Cecil Vyse, engagementHighlights, class tensions]
-
A.
highlightsType
Indicates that one entity serves as a representative example or instance of the type or category defined by another entity.
-
B.
highlightsSign
Indicates that one entity visually emphasizes or draws special attention to a sign.
-
C.
highlights
Indicates that one entity draws special attention to, emphasizes, or visually marks another entity as important or noteworthy.
-
D.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
E.
engagementCapability
Indicates the ability or capacity of one entity to initiate, conduct, or sustain an interaction or engagement with another entity.
- 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_69f76e2d7e8c8190bac4e90734566799 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b35e32d481909ef0220e6f6ff4a8 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2c66054819083897e25edb65ba7 |
completed | May 3, 2026, 8:40 p.m. |
Created at: May 3, 2026, 4:07 p.m.