Triple
T9358241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The May-Pole of Merry Mount |
E225203
|
entity |
| Predicate | contrastsGroup |
P40635
|
FINISHED |
| Object | Merry Mount revelers |
—
|
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: Merry Mount revelers | Statement: [The May-Pole of Merry Mount, contrastsGroup, Merry Mount revelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contrastsGroup Context triple: [The May-Pole of Merry Mount, contrastsGroup, Merry Mount revelers]
-
A.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
B.
opposedByGroup
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
-
C.
achievesContrast
Indicates that one entity creates or enhances a visual or conceptual difference relative to another entity.
-
D.
registerContrast
Indicates that an entity records or establishes a distinction or difference between two or more items or states.
-
E.
createsContrastIn
chosen
Indicates a relationship where one element is used to highlight or emphasize differences with another element within a given context.
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4ff19ab48190a8d85c8ac2644c89 |
completed | April 1, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.