Triple
T3075231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steel Curtain defense of the 1970s |
E64119
|
entity |
| Predicate | positionGroupEmphasis |
P29748
|
FINISHED |
| Object | defensive line |
—
|
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: defensive line | Statement: [Steel Curtain defense of the 1970s, positionGroupEmphasis, defensive line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionGroupEmphasis Context triple: [Steel Curtain defense of the 1970s, positionGroupEmphasis, defensive line]
-
A.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
B.
positionGroup
chosen
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
-
C.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
D.
strategyEmphasis
Indicates an entity’s primary focus or priority within a broader strategy or plan.
-
E.
positionSpecific
Indicates that something applies only at, or is defined with respect to, a particular position or location within a larger structure or sequence.
- 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.