Triple
T26966631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EXPTIME |
E679188
|
entity |
| Predicate | typicalProblemDomain |
P24492
|
FINISHED |
| Object | generalized board 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: generalized board games | Statement: [EXPTIME, typicalProblemDomain, generalized board games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProblemDomain Context triple: [EXPTIME, typicalProblemDomain, generalized board games]
-
A.
typicalProblem
Indicates that a situation, issue, or obstacle is representative or characteristic of the usual problems encountered in a given context.
-
B.
typicalDomain
chosen
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
C.
problemType
Indicates the specific category or classification of a problem within a defined problem space or system.
-
D.
solutionDomain
Indicates the conceptual or practical area in which a particular problem is addressed or solved.
-
E.
concernsDomain
Indicates that something (such as an action, statement, or item) is about, relates to, or is focused on a particular domain or field.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: April 27, 2026, 6:36 a.m.