Triple
T3075230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steel Curtain defense of the 1970s |
E64119
|
entity |
| Predicate | scheme |
P4621
|
FINISHED |
| Object | 4–3 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: 4–3 defense | Statement: [Steel Curtain defense of the 1970s, scheme, 4–3 defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scheme Context triple: [Steel Curtain defense of the 1970s, scheme, 4–3 defense]
-
A.
code
Indicates that an entity writes, develops, or produces computer software or source code.
-
B.
architecture
chosen
Indicates the structural design or organizational framework that defines how components of a system or entity are arranged and interact.
-
C.
logicSystem
Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
-
D.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
E.
codeNature
Indicates that one entity characterizes or specifies the type, category, or inherent nature of another entity, often in a coded or standardized form.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada150d8e08190bde5f68e800e8feb |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.