Triple
T16402799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuhn’s theorem |
E398341
|
entity |
| Predicate | relatesForm |
P123286
|
FINISHED |
| Object | extensive-form game |
—
|
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: extensive-form game | Statement: [Kuhn’s theorem, relatesForm, extensive-form game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatesForm Context triple: [Kuhn’s theorem, relatesForm, extensive-form game]
-
A.
relatedForm
Indicates that one entity is an alternative or variant form of another, such as a different spelling, inflection, or closely related lexical form.
-
B.
referenceForm
Indicates that one entity serves as a reference or canonical form for another entity, typically used as the standard or authoritative version to which others relate.
-
C.
associatedWithForm
Indicates a relationship in which something is linked or connected to a particular form, document, or structured representation.
-
D.
formsWith
Indicates that one entity combines or associates with another to create or constitute a joint structure, group, or configuration.
-
E.
formsFrom
Indicates that one entity is created, derived, or takes shape as a result of another 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d0652081908f42f78b156f3ae7 |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.