Triple
T34785165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin Defense |
E1002784
|
entity |
| Predicate | typicalResultProfile |
P205557
|
FINISHED |
| Object | high drawing ratio in elite play |
—
|
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: high drawing ratio in elite play | Statement: [Berlin Defense, typicalResultProfile, high drawing ratio in elite play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResultProfile Context triple: [Berlin Defense, typicalResultProfile, high drawing ratio in elite play]
-
A.
typicalProfile
Indicates that an entity represents the standard or most representative profile or pattern for another entity.
-
B.
typicalHeadProfile
Indicates that an entity has a head shape or outline that conforms to a standard or commonly observed profile for its type.
-
C.
typicalRedProfile
Indicates that an entity exhibits a characteristic or standard pattern commonly associated with the color red.
-
D.
typicalProfileWhite
Indicates that an entity exhibits characteristics or attributes that are typical of a white profile or category.
-
E.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
- 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.