Triple
T34785133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Defense |
E1002784
|
entity |
| Predicate | belongsToOpeningFamily |
P185229
|
FINISHED |
| Object | Open 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: Open Games | Statement: [Berlin Defense, belongsToOpeningFamily, Open Games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOpeningFamily Context triple: [Berlin Defense, belongsToOpeningFamily, Open Games]
-
A.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
B.
hasOpeningFamily
chosen
Indicates that one entity features or includes another entity as its initial or introductory part, such as an opening section or starting segment.
-
C.
belongsToLegalFamily
Indicates that one entity is a member of, or is legally affiliated with, a particular legal family or legal system tradition.
-
D.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within it.
-
E.
ownsByFamily
Indicates that ownership of an entity is held collectively or primarily by a family rather than by an individual or non-family organization.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: May 3, 2026, 3:59 p.m.