Triple
T28997808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMNLP |
E736213
|
entity |
| Predicate | proceedingsAccess |
P167390
|
FINISHED |
| Object | open access |
—
|
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: open access | Statement: [EMNLP, proceedingsAccess, open access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceedingsAccess Context triple: [EMNLP, proceedingsAccess, open access]
-
A.
proceedingsAre
Indicates that certain events, actions, or legal steps constitute or are recognized as formal proceedings.
-
B.
publishesProceedingsFor
Indicates that an entity (such as a publisher or organization) produces and makes publicly available the official proceedings for a particular event, conference, or meeting.
-
C.
coversProceedings
Indicates that one entity reports on, documents, or provides coverage of a set of proceedings or events involving another entity.
-
D.
proceedingsPublishedBy
Indicates that a set of proceedings (such as from a conference or event) is published by a particular publisher or publishing entity.
-
E.
proceedingsIndexedIn
Indicates that a set of proceedings is included and recorded in a specific indexing service or database.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 9:32 a.m.