Triple
T7964950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summer Exhibition |
E185178
|
entity |
| Predicate | submissionPolicy |
P67136
|
FINISHED |
| Object | open submission |
—
|
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 submission | Statement: [Summer Exhibition, submissionPolicy, open submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submissionPolicy Context triple: [Summer Exhibition, submissionPolicy, open submission]
-
A.
hasSubmissionPolicy
chosen
Indicates that an entity is associated with a specific set of rules or conditions governing how submissions to it must be made.
-
B.
subscriptionPolicy
Indicates the rules, terms, and conditions that govern how a subscription is obtained, used, renewed, or terminated between parties.
-
C.
boardingPolicy
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
-
D.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
E.
submissionBasis
Indicates the basis, criteria, or grounds on which something is submitted or filed (e.g., a document, application, or claim).
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ba0da588190853dda68bba0755a |
completed | March 31, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69cb0473d7dc8190a25d0cf460b9fcbe |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:12 p.m.