Triple
T20655971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tampa 2 defensive scheme |
E507626
|
entity |
| Predicate | usesBaseFront |
P140939
|
FINISHED |
| Object | 4–3 defensive front |
—
|
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: 4–3 defensive front | Statement: [Tampa 2 defensive scheme, usesBaseFront, 4–3 defensive front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBaseFront Context triple: [Tampa 2 defensive scheme, usesBaseFront, 4–3 defensive front]
-
A.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
B.
usedOnFront
Indicates that something is applied, displayed, or positioned on the front side or front-facing part of another object or entity.
-
C.
hasFront
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
D.
usesBaseline
Indicates that one entity relies on or applies another entity as a reference baseline for comparison, measurement, or evaluation.
-
E.
hasFrontFeature
Indicates that an entity possesses a specific characteristic, component, or attribute located on its front side.
- 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_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. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.