Triple
T20656010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa 2 defensive scheme |
E507626
|
entity |
| Predicate | variationOf |
P4680
|
FINISHED |
| Object | traditional Cover 2 defense |
—
|
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: traditional Cover 2 defense | Statement: [Tampa 2 defensive scheme, variationOf, traditional Cover 2 defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variationOf Context triple: [Tampa 2 defensive scheme, variationOf, traditional Cover 2 defense]
-
A.
variant
chosen
Indicates that one entity is an alternative form, version, or variation of another entity.
-
B.
varietyOf
Indicates that one entity is a specific type, kind, or variant of another, more general entity.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
yieldsViaVariation
Indicates that one entity produces or results in another through a process of variation or modification.
-
E.
notableVariation
Indicates that one entity represents a significant or noteworthy deviation or difference from another entity within 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ed48308190b9350a323b9a7952 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.