Triple
T2112959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Year’s Eve |
E42544
|
entity |
| Predicate | commonlyMarkedBy |
P34854
|
FINISHED |
| Object | countdown to midnight |
—
|
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: countdown to midnight | Statement: [New Year’s Eve, commonlyMarkedBy, countdown to midnight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyMarkedBy Context triple: [New Year’s Eve, commonlyMarkedBy, countdown to midnight]
-
A.
reportedMarks
Indicates that an entity has formally communicated or submitted the marks/grades of another entity (such as a student or assessment) to a relevant party or system.
-
B.
moreCommonIn
Indicates that something occurs with greater frequency or prevalence in one group, context, or location than in another.
-
C.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
D.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
-
E.
markType
Indicates the specific category or kind of mark associated with or applied to an 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb0495d0819097dc936540743b74 |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:43 p.m.