Triple
T17148071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NET |
E416145
|
entity |
| Predicate | excludesFromCalculation |
P3119
|
FINISHED |
| Object | exhibition games |
—
|
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: exhibition games | Statement: [NET, excludesFromCalculation, exhibition games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludesFromCalculation Context triple: [NET, excludesFromCalculation, exhibition games]
-
A.
excludedFrom
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
B.
excludes
chosen
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
-
C.
exclusionBasis
Indicates the reason or criterion used to exclude an entity from a set, process, or consideration.
-
D.
excludesAward
Indicates that one entity explicitly omits or disqualifies another entity from receiving a particular award.
-
E.
excludesFromEvidence
Indicates that something is intentionally omitted or disallowed from being considered as evidence in 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f404f0e88190b7ac9ac523fdc7da |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.